mixphix
mixphix
Pull requests are welcome.
The current documentation already points to `read`, but `readFloat` is used in a `ReadS` context that `read` can't replicate. It's better to fix the function to continue allowing parsing floating...
I agree that the most sensible solution is to export it from `GHC.Exts` as the module hierarchy currently stands, if they are to be so stable and widely-used. Would that...
> Somebody has to maintain them, and GHC HQ is sufficiently stretched already that it isn't reasonable to add maintenance burden alongside GHC releases. Somebody has to maintain `base`, too....
For one thing, `GHC.IO.Device.dup :: IODevice a => a -> IO a` already exists in `base`, so we will have to bikeshed the name already. There is nothing blocking `arr2`...
These seem like useful arrow-related functions, I think exporting them from `Control.Arrow` (with `dup` at its arrow type `Arrow arr => arr a (a, a)`) would be fine.
Have you encountered [`ListT`](https://hackage.haskell.org/package/list-t-1.0.5.7/docs/ListT.html)? ```hs newtype ListT m a = ListT (m (Maybe (a, ListT m a))) ``` It even offers `unfoldM :: Monad m => (b -> m (Maybe...
Impact assessments are appreciated, though I myself have not been able to successfully build a working version of `clc-stackage` in some time. For a function with Hackage hits in heavy-duty...
Please do include documentation in your merge request, if you choose to create one.