-
Notifications
You must be signed in to change notification settings - Fork 15
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
Overloaded record names #117
Comments
Adding -XDisambiguateRecordFields doesn't help. |
It looks like anyway, I'd reckon that using prefixed names really could help the reader of the code to understand which record field is actually been used |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Initially I thought that Haskell's overloaded record extension meant I could e.g., put a field called "eqs" in many records, as is customary in AQL Java. And it can, but the actual call sites of these overloaded projection functions appeared not to use type information to resolve which package/namespace to use, and so I started giving them ad hoc names rather than write prefixes (e.g., Instance, Schema) to disambiguate. Anyway, the goal of this issue is to normalize the naming scheme for the record components.
The text was updated successfully, but these errors were encountered: