#13013: Add readMaybe to Prelude (possibly readEither too), make Haddocks for read more cautionary -------------------------------------+------------------------------------- Reporter: sjakobi | Owner: Type: feature request | Status: new Priority: normal | Milestone: Component: Core Libraries | Version: Resolution: | 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: | -------------------------------------+------------------------------------- Comment (by sjakobi): Replying to [comment:4 ekmett]:
I'm personally weakly against this proposal as names are very much not taken by `Prelude` lightly.
That said, this belongs as a `libraries@` mailing list proposal at this stage, rather than as a ticket here. If clear consensus arises from the `libraries@` proposal, ''then'' this would become the correct venue to put
To be clear, the issue is that the newly exposed `readMaybe` and `readEither` names could clash with pre-existing definitions that use the same names, right? the feet of the core libraries committee to the fire to get it implemented. Actually I wanted to send this proposal directly to the libraries mailing list, but then decided otherwise after reading [https://wiki.haskell.org/Library_submissions#Guide_to_proposers this "guide for proposers"]. If that guide is out of date, it would be great if someone could update it to reflect the current practice. I'll write the email in a few days once I'm back from Christmas holidays. Would a discussion period of 4 weeks be appropriate? -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/13013#comment:5 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler