-
Notifications
You must be signed in to change notification settings - Fork 126
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
Panic when resolving type fixities #614
Comments
Here's a minimized example:
Writing |
The source of the problem is the call to The comment there, "it's a real error if the fixities didn't work out" is just wrong. If we have any operators to have non-associative fixities, there will always be the possibility of users chaining them together like I was thinking of replacing the call to |
The link to the source code in the previous post is broken; here's a new permalink to a current version: cryptol/src/Cryptol/ModuleSystem/Renamer.hs Lines 640 to 643 in 67fc367
|
In a type such as
f : {m, n, k} (n == max 2 m, k == m + 1) => [m] -> [k][n]
, if I were to accidentally omit the comma in the constraints as so:Cryptol will crash instead of reporting a parse error or malformed type:
The text was updated successfully, but these errors were encountered: