Comments (5)
In the general case, mutating a parent rule's variable isn't safe due to backtracking, so it's not supported.
The *
operator collects its children into a Vec by default, so your case could be rewritten:
document -> Document
= children: block*
{ Document { children: children } }
block -> Element
= ...
where Document.children has type Vec<Element>
. It might be possible to make it generic over some Container trait rather than requiring the use of Vec.
from rust-peg.
And if you want to mutate a variable within the same rule, the rule action has ownership, so it can move it into a mutable variable:
document -> Document
= children: block* {
let mut children = children;
children.push(another_element());
Document { children: children }
}
from rust-peg.
Alright, that might work for the basic use case presented in the initial post, but the structure of my program is such that the block
rule from above also calls other rules, which, in turn, may return Element
s themselves.
If the rules that block
calls return a Vec<Element>
as well, how would I then add that to the Vec<Element>
children
?
from rust-peg.
One way would be to have block
return Vec<Element>
and have the document
rule concat_vec
the Vec<Vec<Element>>
it receives. Yes, it allocates more than a single vector, but matches need to be independent to be able to backtrack.
from rust-peg.
Alright I'll try that. Thanks!
from rust-peg.
Related Issues (20)
- warn on missing .PHONY entry for common target names HOT 1
- feature request: a way to query the current line number during parsing HOT 5
- general question about thread safety HOT 1
- Use tracing rather than println?
- Binding captured strings? HOT 6
- help with misleading expected set HOT 2
- How do I escape the dot character in [^ pat]? HOT 1
- rustc warning about unused imports HOT 1
- Make the TokenStream wrappers used internally available
- How to escape the " HOT 3
- Mutual recursion with `#[cache_left_rec]` fails
- Case-insensitive literal matches throw off error position HOT 6
- `{? Err("x") }` should not be considered nullable for infinite loop check
- the `#[proc_macro]` attribute is only usable with crates of the `proc-macro` crate type HOT 2
- Automatic whitespace handling? HOT 1
- "rule" but not when HOT 2
- Error recovery when using `precedence!` HOT 2
- What about presenting on Rust Ukraine Conference 2024?
- feat: in rule where clauses support
- feat: mut variable syntax support for TaggedExpr and RuleParam HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rust-peg.