-
Notifications
You must be signed in to change notification settings - Fork 119
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 naming doesn't propagate through records #1019
Comments
FWIW, similar behavior with tuples. I suspect this is down to some detail regarding how unification works in the typechecker causing a unification variable to end up with an autogenerated name.
|
This is exactly the behavior I would expect. I'll try to explain what's happening here: Because I guess what you'd rather have is for the preferred name to based on the original parameter name when the polymorphic variable was instantiated. For example, the instantiated I actually don't think it's the best idea to do this everywhere, as I think the results would often be messy and/or surprising. For example, during typechecking, two unification variables |
I don't think we're planning to do anything about this. |
The text was updated successfully, but these errors were encountered: