Error recovery #10
Labels
Comments
ollef
added a commit
that referenced
this issue
Dec 29, 2018
This refactors the compiler from a push-based, more traditional, pipeline, to a pull- and query-based architecture built on a build system library made for the purpose, inspired by Shake and the Build systems a la carte paper: https://github.com/ollef/rock This will enable parallel and incremental builds in the future and will help solve #10, #13, and #26. This also implements some improvements that were necessary along the way to get the tests to pass, for example: * Recover from all errors (barring bugs), fixing #10. * Improve logging with logging prefixes for selective printing. * Fix some tests that were wrong. There's still some stuff to refactor and fix up, but since the tests now pass I think it's a good time to get it merged.
|
Mostly done in #119. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Throughout the whole frontend (parser and typechecker especially) we should try to continue working even in the face of errors. We should insert coercion terms that throw errors if something that errored is used, but otherwise try our best to create a runnable program even when there are errors, a la deferred type errors.
This means that we can report multiple errors (which is important for tooling), and that we can test programs while they're being written.
The text was updated successfully, but these errors were encountered: