#14581: coerce String type in annotations with OverloadedStrings enabled -------------------------------------+------------------------------------- Reporter: mgmeier | Owner: (none) Type: feature request | Status: closed Priority: low | Milestone: Component: Compiler | Version: 8.2.1 Resolution: invalid | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Changes (by RyanGlScott): * status: new => closed * resolution: => invalid Comment: Replying to [comment:1 mgmeier]:
Addendum: or is the general idea of annotations that you should be able to annotate some definition with ''any'' Haskell value?
Yes. [https://downloads.haskell.org/~ghc/8.2.2/docs/html/users_guide/extending_ghc... #annotating-values Per the users' guide:]
Any expression that has both `Typeable` and `Data` instances may be attached to a top-level value binding using an `ANN` pragma.
Thus both `String` and `Text` could be used in an `ANN` pragma, so you'd need to resolve the ambiguity yourself. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/14581#comment:2 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler