Li Jin

You're right. Explist could handle line break by itself. But backslash can be used after function name or used to write lines start with operator. ``` some_long_named_function_call_one \ some_long_named_function_call_two \...

The compiler should now give the detailed error by newest commit. ```sh 1: write invoke arguments in parentheses without leading spaces or leading spaces without parentheses assert (1==1, "Oopsies!") ^...

I can not find the import feature you mentioned in official doc http://www.lua.org/manual/5.4/. Can you provide a link or something to get me informed?

"import" is treated as a keyword for the moment, but I can try to change that. And supporting 'import("module")' as a function call in Yuescript.

Digging around the parser rules a little while, I'm thinking of adding special aliasing syntax like: ```moonscript `import "abc" -- the backtick will turn keyword import to variable name ```...

@SlashScreen > Fair point, perhaps I was mistaken. Playdate's embedded Lua only uses the `import` keyword, not `require`. Right now I've been trying to do this with macros, but since...

Confirmed this performance issue with continuously nesting table literals. Found that it's caused by not arranging the orders of syntax parsing rules properly. Commit 0cc452c7cf2301e75bab1069c9da6ee73c7c5cfd should have fixed this. Before...

Found it was a redundant PEG syntax back trace issue which happened in rule `ChainValue`. When the parser failed to check rule `Callable >> ChainItems`, it fell back to check...

The nested syntax parser tree is leaving lots of fallback patterns to try, that causes the unclosed `{{{{{{{{` expression taking a pretty long match to fail. Added a stoping rule...

Tried fixing all similar issues by limiting nested expressions parsing depths to 100 levels. The parser is written in a parser combinator which is spawning lots of recursive function call...