On 23/04/2014 20:04, dm-list-haskell-librar...@scs.stanford.edu wrote:
Edward Kmett ekm...@gmail.com writes:
You can wind up in perfectly legitimate situations where the name for the
type you are working with isn't in scope, but where you can write a
combinator that would infer to have that
Not sure.
An even simpler case is something like exporting a Traversal but not
exporting Data.Traversable, which appears in the expansion, etc.
These sorts of things happen in code using lens. Older versions of lens
didn't export all of the types needed to write out the type signature long
hand
Er.. my mistake. Control.Applicative.
That is what it is we don't re-export that is used in Traversal. =)
On Wed, Apr 30, 2014 at 2:47 AM, Edward Kmett ekm...@gmail.com wrote:
Not sure.
An even simpler case is something like exporting a Traversal but not
exporting Data.Traversable, which
John Lato-2 wrote
I'd like to compile ghc-7.8.2 with DynamicGhcPrograms disabled
Are you able to use template haskell (and qusiquoting) with this? Don't they
need dynamic libs?
--
View this message in context:
For people keeping score, I created a branch with this already done
the other day:
https://github.com/ghc/ghc/tree/wip/kill-extcore
Again, unless someone speaks up *real* soon, I'm probably going to get
rid of it before the end of the week - so your timeframe is something
like 72 hours to make a
+1
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
