Closed maerten closed 2 years ago
Thanks for reporting this! And appreciate the leg work on finding the related issue, that really helps. I've got a PR #115 going that will get 9.4 into CI (and picks up some others).
I was hoping this one would be a simple one, but I currently can't see a way to use selectors at all if two records define the same selector in the same module.
As of GHC 9.4.1, selector names have to be entirely unambiguous.
and
An unqualified name "x" is unambiguous if and only if there is just one "x" in scope unqualified.
The DisambiguateRecordFields
only has an effect on matching and constructing, no effect on selectors.
I'll keep looking into this, hopefully there's a way to make this work without a breaking change.
Just released 1.0.0.1 which fixes this issue, and 9.4 is now part of the CI. Answer was to use pattern matching, as GHC can still disambiguate that.
Thanks again for the report!
Wow that was fast, thanks for fixing it!
Hello, it seems that compiling on GHC 9.4 fails. Possibly related to: https://gitlab.haskell.org/ghc/ghc/-/merge_requests/7639