-
Notifications
You must be signed in to change notification settings - Fork 6
Error recovery mecanism #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
pmderodat
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To summarize our live discussion:
Darn, I did not mean to introduce an interactive behavior in the interpreter! ;-) No big deal, let’s keep it this way for now. One more topic for the general design discussion we’ll have next week with Raphaël.
The stream of changes indicates that we need the testsuite to be useful at detecting regressions (for instance the one fixed in d65dcf6) but also as an executable example of how the interpreter behaves.
So let’s add a light code coverage feature to the testsuite (similar to gnatcoll-core’s) and add tests for uncovered parts of the interpreter. This will be tremendously useful to control the refactorings to come. :-)
Thanks a lot for your efforts!
Add an implication construction in LKQL Closes #4 See merge request eng/libadalang/langkit-query-language!275
No description provided.