Open
Conversation
Feature: implemented lua like errorsFeature: implemented Lua like errors
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Features
error::ErrorWithStackTrace]stdlib,meta_ops.rs,parser.rs,lexer.rs, etc.Parser] logic for improved error handling.Lexer] logic for improved error handling.stdlib.goldenscriptsand some tests.Why is this needed?
Current errors in
piccoloprovide neither extensive information nor anything at all - the current parser provides no information about why an error occurred, where it occurred, and how it occurred, and the number of errors is very, very limited. Errors in stdlib are not standardized: some look like those in PUC-Rio Lua, others seem to be written "off the cuff"A few examples
How it was before:
How it is now:
all examples were taken from /examples/interpreter.rs