-
Notifications
You must be signed in to change notification settings - Fork 165
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
Make closingToken
function pattern matching exhaustive
#399
Conversation
Mmh, I am not sure. This gives a better error message, but still |
In the round-trip test the layouts are resolved once, before the first parsing. |
Now I finally found a small reproducer:
Input:
Error is:
This seems to be a problem with the implementation of |
Layout stop words will now do not have any special effect when in the top layout block (column 1). Fixes a problem where they triggered an exception.
Layout stop words will now do not have any special effect when in the top layout block (column 1). Fixes a problem where they triggered an exception.
The
closingToken
function cases in the layout solver were not exhaustive