RE: [commit: base] master: Implement "TypeLevelReasoning" proposal at wiki:TypeLevelReasoning (365b9d8)

2013-07-24 Thread Simon Peyton-Jones
Hs-boot files tend to get in the way of optimisation. Moreover, sometimes they are truly necessary, and if there are un-necessary ones that can greatly complicate adding necessary ones. There are already LOTS of data types declared as instances of Typeable at the place that Typeable class is d

Re: GHC head and .haddocks

2013-07-24 Thread Ian Lynagh
Hi Edsko, On Tue, Jul 23, 2013 at 12:38:25PM +0200, Edsko de Vries wrote: > > I'm trying to build and install ghc head, with the installation of the > .haddocks. I'm running into all kinds of trouble though. I have > docbook and docbook-xsl installed, docbook isn't related to building haddock d

Re: [commit: base] master: Implement "TypeLevelReasoning" proposal at wiki:TypeLevelReasoning (365b9d8)

2013-07-24 Thread Richard Eisenberg
I agree that hs-boot files are a little inelegant, but is there a bigger problem with them? I consider instances to be more tied to a datatype definition than the class definition. It may be possible (I think it is) to avoid the Proxy.hs-boot and Equality.hs-boot files if we scatter their insta

RE: [commit: base] master: Implement "TypeLevelReasoning" proposal at wiki:TypeLevelReasoning (365b9d8)

2013-07-24 Thread Simon Peyton-Jones
Richard I am deeply suspicious of all these hs-boot files. Instances should preferably go EITHER with the data type declaration OR with the class declaration. In the case of Proxy, for example, why can't the Typeable instance for Proxy go in Data.Typeable.Internals? (And perhaps similarly fo

Re: haddock: internal error: synifyKind

2013-07-24 Thread Simon Marlow
That seems to have fixed it. Thanks! Simon On 24/07/13 13:17, Richard Eisenberg wrote: My fault -- sorry. Forgot to push the change to haddock when I pushed base. Update your haddock, and you should be OK. Richard On 2013-07-24 13:10, Simon Marlow wrote: A validate today on x86_64/Linux is

RE: new-typeable, new cast?

2013-07-24 Thread Richard Eisenberg
Of course -- that worked. I was very muddled in my thinking yesterday, figuring that the error was legitimate. Thanks, Richard On 2013-07-23 20:11, Simon Peyton-Jones wrote: I'd suggest using "WithinType" as the argument to synifyType that's currently an error call in Haddock.Convert line 356

Re: haddock: internal error: synifyKind

2013-07-24 Thread Richard Eisenberg
My fault -- sorry. Forgot to push the change to haddock when I pushed base. Update your haddock, and you should be OK. Richard On 2013-07-24 13:10, Simon Marlow wrote: A validate today on x86_64/Linux is failing with haddock: internal error: synifyKind While haddocking the base package.

haddock: internal error: synifyKind

2013-07-24 Thread Simon Marlow
A validate today on x86_64/Linux is failing with haddock: internal error: synifyKind While haddocking the base package. Anyone know why? Cheers, Simon ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/g

Re: Repo permissions broken

2013-07-24 Thread Simon Marlow
On 23/07/13 00:04, Ian Lynagh wrote: On Mon, Jul 22, 2013 at 03:51:49PM -0700, Iavor Diatchki wrote: changing the default umask on the entire server is not necessary to fix this problem. Git already has support for exactly this use case Well, I don't mind if someone wants to do the git thing

Re: Exposing newtype coercions to Haskell

2013-07-24 Thread Joachim Breitner
Hi, Am Dienstag, den 23.07.2013, 18:58 + schrieb Simon Peyton-Jones: > If you add -XIncoherentInstances *just to the module that has instance > IsNT a a*, then it'll work fine I think. This says "pick this > instance even though an instantiation of the constraint might match a > more specific