Felix S.

Hmm, there is one way to have a variable be `close` and `const` simultaneously… ```lua local x = ... local x = x ``` Kind of verbose, but works. (The...

Never mind, `` is going to imply `` anyway. So multiple attributes are a non-issue for now. Another change is that labels from inner scopes will no longer be allowed...

Another change is that UTF-8 escapes now allow to specify code points up to U+7FFFFFFF, as in the 1993 definition of UTF-8 instead of the modern one. (Surrogate code points...

`"\u{7FFFFFFF}"` is simply the same string as `"\xFD\xBF\xBF\xBF\xBF\xBF"` in Lua 5.4. As for how it's supposed to be interpreted as a Unicode string, that is another matter; #68 has more...

@TwoLivesLeft No need for that, probably. I have the code already written in my private branch, all that remains is to write the tests.

I think I am going to solve this and #9 in one go. In other words, I will create a callback that shall receive diagnostics from the parser as a...

As of 6f8a7ea28c04f4e31d6ab88b9ce56f39359589d9, the error type thrown by the parser is exported as a `SyntaxError` export. Users are encouraged to use that export instead of directly referring to the engine’s...

I will probably add a switch to toggle between these modes: - no interpretation for string literals at all; extended identifiers not mangled - pseudo-ISO-8859-1/`x-user-defined` (option 0) - UTF-8 (either...

Got some WIP code that implements an `encodingMode` option, allowing to switch between: - current behaviour - no mangling for identifiers, `.value` of string literal nodes is `null` - ISO-8859-1...

I changed my mind; I won't keep current behaviour as the default, maybe I won't even keep it as an option; nobody seems to expect or desire it anyway. The...