boyned//Kampfkarren

I can't remember, what syntax was added in Lua 5.3? I thought it's big feature was integers, which I don't think matter on a syntax level.

Bitwise ops, that's what it was, thanks!

Possibly! I'm okay with this at first glance.

To be clear, have you ever gotten this on release optimizations, or is that just theoretical? If so, then my potential fix likely won't help.

Yeah, this is one I'm going to end up taking on my own at some point. I put a thread on the Rust forums and was told to use something...

I believe Lua raises a syntax error as well, which we want to match.

This solves #47 because ideally, the API is something like this: ```rust let parser = full_moon::new_parser() .with_extension(full_moon_luau_ext::LuauExtension::new()) .build(); parser.parse(code); ``` This allows you to combine multiple extensions if you want,...

Update on this. I think structs will look like this: ```rs struct LocalAssignment { local_token: Token, // Perhaps Token? // etc... assignment: Expression, // For sake of example... plugin_provided_info: P,...

Requirement before 1.0 is a bit much IMHO--my goals for 1.0 was solid immutable and mutable parsing, which we're just about finished with, save some API quirks. I think this...

Some of these can be attributed to using the wrong attributes, i.e. not using `#[visit(contains = "...")]` or `#[node(full_range)]`, see: https://github.com/Kampfkarren/full-moon/blob/814b7f9411565f3596a6d113021bc4e1e9883292/full-moon/src/ast/mod.rs#L215-L221 Most should probably just manually implement the trait though,...