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

Get rid of NoValue. More use of Errors in parser #14

Open
mneumann opened this issue Feb 15, 2014 · 0 comments
Open

Get rid of NoValue. More use of Errors in parser #14

mneumann opened this issue Feb 15, 2014 · 0 comments
Assignees

Comments

@mneumann
Copy link
Owner

Clean up the code to use proper parse errors, also including the filename/line number. Don't return NoValue in case of an error, instead return a proper Error. Maybe also differentiate between a SyntaxError and a SemanticError (e.g. duplicate section).

Also make use of unreachable!() macro instead of assert!(false) in some places.

@mneumann mneumann self-assigned this Feb 15, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant