On Mon, Oct 29, 2012 at 11:07 PM, Gabor Greif wrote:
> IIRC, I had to manually remove a 'Parser.y' file to get things rolling.
>
That's exactly it. I just ran into this problem myself. It's due to a
recent change that meant Parser.y was not getting removed/rebuilt in its
old location.
http://hac
I have been getting the following message from
cvs-ghc-owner@haskell.orgrepeatedly since December: "Your membership
in the mailing list Cvs-ghc has
been disabled due to excessive bounces."Lately, it's been every four days. I
then have to re-enable it every time. Not a difficult thing, but the
repet
> * We probably want to replace the frames with something more modern
> (like a sidebar on the same page) in the future
>
> * We are rewriting the HTML backend and it would be nice to avoid
> unnecessary work
>
> So if you're using this feature and want to keep it, please speak up!
>
Somewhat OT
Hi Daniel,
> Basically, I added cmm bindings to mpz_powm(_ui), mpz_tstbit, and
> mpz_sizeinbase. The modular exponentiation function is significantly
> faster than anything I could find in pure haskell, and the bit testing
> is way more efficient than the default Data.Bits implementation
> involv
> | Incidentally, it might be worth breaking proposal 1 into two separate
> | proposals: It would be useful to be able to disambiguate imports/exports
> | even if we don't change the lexical rules for types, as it would allow
> | the class and type namespaces to be separated.
>
> I don't advocate s
> As we push the boundary on Haskell's type system, so that types and values
> blur a bit more, Haskell's deliberate overlapping of type constructor and
> data constructor name space is becoming a little awkward. Syntax is
> tiresome, but it's unavoidable.
>
> I've written down the issues and mad
> | Would it be useful if I tried to get hold of such a thing, intending to
> run it
> | (and make it available) in the same manner as I do the tnaur PPC 2
> machinery,
> | including the above suggestions? The PPC Mac OS X's seem to be be on the
> way
> | out, so something would have to be done abo
Hi,
I'm fixing http://hackage.haskell.org/trac/ghc/ticket/2467
>
Since you bring up orphans, I have a more general question regarding them
that came up recently.
The design of a library I'm working on requires orphan modules. After
reading the GHC user's guide, I believe that orphans are (only)
