Ah, well, yes, if you want to get an existing, *uncompiled* module into the
ambient context, then of course you must compile it. Glad you are unstuck.
Simon
| -Original Message-
| From: Ranjit Jhala [mailto:rjh...@eng.ucsd.edu] On Behalf Of Ranjit Jhala
| Sent: 27 April 2011 00:42
| To:
On 11-04-26 05:05 PM, Brandon Moore wrote:
There are already hashes to keep incompatible builds of a package separate.
Would anything break if
existing packages were left alone when a new version was installed? (perhaps
preferring the most
recent if a package flag specifies version but not hash).
Hi,
While trying to figure out why some of my code is very slow I have found
that it is something related to division.
Digging a bit deeper I found an example which shows some unexpected
magic and a lack of the expected one.
Before raising any tickets in trac I would like to consult with you
r
On April 27, 2011 23:01:50 Denys Rtveliashvili wrote:
> Question 1: what is the meaning of those magic numbers
> -9223372036854775808, -6677706553, -7418931981405, -8257271295304186?
> Question 2: under which circumstances those strange branches of
> execution will be used and what those results wo
> From: Albert Y. C. Lai
> To: glasgow-haskell-users@haskell.org
> Sent: Wed, April 27, 2011 9:53:38 PM
> Subject: Re: Package management
>
> On 11-04-26 05:05 PM, Brandon Moore wrote:
> > There are already hashes to keep incompatible builds of a package separate.
> > Would anything break if
>
