Skip to content
This repository has been archived by the owner on Jan 24, 2020. It is now read-only.

Error reporting #15

Open
LPGhatguy opened this issue Apr 24, 2018 · 3 comments
Open

Error reporting #15

LPGhatguy opened this issue Apr 24, 2018 · 3 comments
Labels
enhancement New feature or request

Comments

@LPGhatguy
Copy link
Owner

Error reporting coverage is pretty spotty, and the idea probably needs to be revisited.

@LPGhatguy LPGhatguy added the enhancement New feature or request label Apr 24, 2018
@pablomayobre
Copy link

pablomayobre commented Apr 26, 2018

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 ❤️

@LPGhatguy
Copy link
Owner Author

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.

@pablomayobre
Copy link

Thank you for your answer, I'm totally looking forward to that in the future!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants