Name clashes in record fields: Difference between revisions
(prime link fix) |
(→Using language extension: fix documentation link for duplicate record fields) |
||
Line 32: | Line 32: | ||
=== Using [[language extension]] === | === Using [[language extension]] === | ||
<code>[https:// | <code>[https://ghc.gitlab.haskell.org/ghc/doc/users_guide/glasgow_exts.html#duplicate-record-fields DuplicateRecordFields]</code> extension (GHC 8.0.1+) allow definition of record types with identically-named fields. | ||
== See also == | == See also == |
Revision as of 19:17, 4 April 2019
Question
error| Multiple declarations of ‘xxx’
I like to define:
data Human = Human {name :: String}
data Dog = Dog {name :: String}
Why is this forbidden?
I like to define:
data Human = Human {name :: String}
name :: Cat -> String
name = ...
Why is this forbidden, too?
Answer
The record field accessors name
are just functions
that retrieve the field's value from a particular record.
They are in the global scope together with top-level functions
and thus cannot have the same name.
For resolving this you may:
- rename the accessor or the top-level function
- put the data declaration or the top-level function in another module and import qualified
- write a typeclass with a
name
function and fit the non-accessor functionname
somehow into that.
Using language extension
DuplicateRecordFields
extension (GHC 8.0.1+) allow definition of record types with identically-named fields.
See also
- Type directed name resolution
- Haskell-Cafe on Record types and unique names