This was
affine-group-literal = "(" group-coordinate "," group-coordinate ")" %s"group"
instead of
affine-group-literal = "(" group-coordinate "," group-coordinate %s")group"
(note the different ending).
This change should have been part of the PR for whitespace in group literals,
but apparently I failed to do that, along with the other changes.
This commit rectifies that omission.
Make this more concise and clear by just presenting the lexical and syntactic
grammar as the way we define the Leo syntax, as opposed to discussing
alternatives like PEGs.
Explicate references to RFCs a bit.
Use the term 'sequence of terminals' instead of 'string' to avoid any confusion.
(Still use 'string' to refer to the actual strings in double quotes that are
part of the ABNF notation itself.)
Update to say that grammar is no longer just a draft.
Put primary motivation and purpose of grammar first.
Mention use in formalization second, and slightly simplify that part, given that
the formalization is not public yet.
This was uncovered by running the grammar through the ACL2 build: among other
things, the build checks that every nonterminal referenced in the right side of
each rule has a definition in the grammar.
620: Feature/254 strengthen import rules r=collinc97 a=gluax
Grammar changes are a bit different than what was suggested in the original feature request #254. However, it should be logically equivalent and I think makes more sense on the rust side.
Closes#254
Co-authored-by: gluaxspeed <jonathan.t.pavlik@gmail.com>
598: [Feature] 374 circuit self access r=collinc97 a=gluax
Feature resolves#374. At the grammar level the following syntax is no longer allowed on self:
```
self[0];
self();
```
Syntax that is allowed at the grammar level is:
```
console.log("b: {}", self::b);
console.log("hmm: {}",self::hmm());
self.hello();
console.log("access: {}", self.a);
```
Note that these changes are only at the grammar level only.
Co-authored-by: gluaxspeed <jonathan.t.pavlik@gmail.com>
Co-authored-by: Howard Wu <9260812+howardwu@users.noreply.github.com>
