David Feuer

It's possible to make the change in a way that's invisible to users, although it can be made visible later. See, for example, Data.Profunctor.Unsafe, which defines the Profunctor class including...

Oh yes, and quit that horrible "Check for empty, then use a partial function to decompose" pattern. On Aug 29, 2016 10:05 PM, "David Feuer" [email protected] wrote: > It's possible...

It's definitely possible to avoid that. At worst, you can use module Public where import qualified Secret gmap :: ... gmap = Secret.gmap but I don't _think_ you have to...

Ugh. I just checked. The easy ways don't work, as you expected (silly design decision that). But the ugly sledgehammer of writing functions implemented using secret methods works just fine....

They absolutely do not need to update their code the first time. Their code will continue to do _exactly_ what it was doing before; the method will simply take its...

You're going to need to wrap all those pieces in CPP restricting in to appropriate `__GLASGOW_HASKELL__` versions.

Glasgow Haskell, because it really relies on GHC-specific features. On Jan 13, 2018 1:33 PM, "Daniel Winograd-Cort" wrote: > Is it a __GLASGOW_HASKELL__ version or is it MIN_VERSION_base(4,9,0)? > >...

You're right; separate PR. I guess I can ask the libraries list. On Jan 15, 2018 12:42 PM, "Daniel Winograd-Cort" wrote: > *@dwincort* commented on this pull request. > ------------------------------...

You may be able to avoid capturing issues by giving the `go` functions full signatures, making it clear they don't take call stacks. Check Core often, maybe look at STG...

Are you making any progress? I'd love to get this into the next release, but that's probably going to happen in the morning!