#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 ekmett):
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?
Yep. Four weeks with the holidays probably makes sense. The phrasing in that section was largely put together to encourage folks patching the larger diaspora of packages that fall under the core libraries committee preview to actually use the issue trackers in question -- mostly because `libraries@` won't care about, say, minutiae about how some combinators in the `unix` package behave on OpenBSD. I probably should add some language encouraging `base`- and especially `Prelude`-affecting proposals to expect to always have to go through `libraries@` as the impact spreads to everyone. Anything submitted here is likely to get maybe 5-10 pairs of eyeballs on it. Submitting to `libraries@` enables a lot more feedback. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/13013#comment:6 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler