Joe Hildebrand

I think we should do a release with #291 in it, then finish the design and implementation of this. This might be big enough to warrant a 3.0, in which...

See https://github.com/arcanis/arpege#automatic-return-values for the original idea.

> * if there are `@` and `;`, error; That won't work quite as-is, because that's currently legal and useful for predicates: ```peg.js foo = @n:$[0-9]+ ! { return n[0]...

I'm not sure about the arrays with extra properties on them yet, I'll need to think about that a little. However it is a very elegant solution.

I see Qix as the only one who said it was too magical, in [this comment](https://github.com/pegjs/pegjs/issues/235#issuecomment-421277323). I think now that we've lived with `@` for a while, `@label:` doing *something*...

> For something that is not often used, I'd suggest `$`. That works for me. > custom `toJSON` Yeah, this is one of several issues we'd need to figure out....

I'm going about this a slightly different way that changes the interface a lot less. There's a special type you'll be able to pass in for `grammarSource`, called `GrammarLocation`, which...

`peg.js` supported many old browsers, and there are a good number of people using it there, from what I can tell. Some of them should probably be pre-compiling their grammars,...

I don't think it needs to be a CLI parameter, as we can use `os.EOL` in the CLI code, and pass that into the API as needed. Normalizing line endings...

We might decide to take some pieces of this, all of it, or continue on to add (perhaps-optional?) support for non-BMP character classes.