-
-
Notifications
You must be signed in to change notification settings - Fork 305
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
type unification regression #733
Comments
Sounds like what I could do is add a new test in txtar format in lang/interpret_test/TestAstFunc1
Then as I go, do Not sure yet what will go in the test mcl file but just wanted to see if this strategy is what you had in mind? |
Sounds perfect! Note that TestAstFunc1 has sub tests, so you can |
FYI: I have a large feature branch which is not yet finished, that totally rewrites type unification and solving, so this issue should probably be ignored for now, until that's merged. With any luck we'll have fixed the bug. |
This simple code used to work. I think I broke it, and it fails at type unification. Add a simple test in TestAstFunc1 and bisect the regression! Bonus points if you have a fix, although please ask for help before digging too deeply into it.
Broken in 7777107
Worked some time not too long ago.
The text was updated successfully, but these errors were encountered: