You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2020. It is now read-only.
Hi! Congrats on this great project, I wanted to ask whether you intend to make this parser abort on error, or continue parsing until all errors are found?
Non-abortive parsers are useful for linting and also for autocomplete providers, I believe that there is no complete solution for these problems out there, using one universal parser. So I was wondering if this was on your scope.
PS: Would love to learn Rust entirely to help you with this, but I still have lots to learn, keep it up ❤️
I think that the first version of the parser will abort on error just so that we can get some tools working sooner, but I definitely want to look into error recovery at statement boundaries. In a lot of languages, you can just ignore tokens after an error until you reach the next semicolon or block end, but Lua doesn't have as clear of information there!
Thanks for bringing up autocomplete providers -- that's probably the best reason to have this sort of support, and definitely something I want to enable.
Error reporting coverage is pretty spotty, and the idea probably needs to be revisited.
The text was updated successfully, but these errors were encountered: