Skip to content

Overloaded record names #117

Open
Open
@wisnesky

Description

@wisnesky
Contributor

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.

Activity

wisnesky

wisnesky commented on Nov 15, 2018

@wisnesky
ContributorAuthor

Adding -XDisambiguateRecordFields doesn't help.

marcosh

marcosh commented on Nov 15, 2018

@marcosh
Contributor

It looks like DisambiguateRecordFields can't do too much (https://downloads.haskell.org/~ghc/8.2.2/docs/html/users_guide/glasgow_exts.html#record-field-disambiguation)

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

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @epost@marcosh@wisnesky

      Issue actions

        Overloaded record names · Issue #117 · statebox/cql