On 25/04/2012 03:17, Mikhail Glushenkov wrote:
Hello Simon,
Sorry for the delay.
On Tue, Apr 10, 2012 at 1:03 PM, Simon Marlowmarlo...@gmail.com wrote:
Questions:
Would implementing this optimisation be a worthwhile/realistic GSoC
project?
What are other potential ways to bring 'ghc -c'
On 25/04/2012 08:57, Simon Marlow wrote:
On 25/04/2012 03:17, Mikhail Glushenkov wrote:
Hello Simon,
Sorry for the delay.
On Tue, Apr 10, 2012 at 1:03 PM, Simon Marlowmarlo...@gmail.com wrote:
Questions:
Would implementing this optimisation be a worthwhile/realistic GSoC
project?
What are
Hi Simon,
First of all, I'm sorry if I'm coming off as too combative,
as Greg says. That is certainly not my intention.
I'm not asking for any free work from you, either.
The only reason I don't like using OverloadedStrings
for typing string literals as Text and ByteString
is that when you turn
On Wed, Apr 25, 2012 at 10:15, Yitzchak Gale g...@sefer.org wrote:
The only reason I don't like using OverloadedStrings
for typing string literals as Text and ByteString
is that when you turn on OverloadedStrings, you turn
it on for all types, not just Text and ByteString.
I don't want to be
One can always use a Maybe to make an IsString literal total. Perhaps this
is what library authors should do in those cases when a fromString
implementation is obviously partial.
i.e. instead of instance IsString XML where ...
define: instance IsString (Maybe XML) where ...
HTH,
Ozgur
On 24
Hi,
On 04/25/2012 09:15 AM, Yitzchak Gale wrote:
Because
all other uses of OverloadedStrings that I have
seen, and there are many, are ill-advised in my
opinion. They all should have been quasiquoters.
But the problem here is that reasonable people may choose to
disagree as to what is
The idea that I currently like the most is to make it possible to save
and load objects in the GHC heap format. That way, deserialisation
could be done with a simple fread() and a fast pointer fixup pass,
which would hopefully make running many 'ghc -c' processes as fast as
a single 'ghc
Hi,
I've just attached my fix for hard-float ABI build failure on GHC HEAD
to the #5914.
I would be more than glad if you can attempt to merge it to 7.4.x you
are packaging and test if it works for you on both soft and hard float
ABI. Hard seems to be preferred these days at least on
Erik Hesselink wrote:
I don't think IsString should be dismissed so easily.
I'm just saying I don't want to be forced to use it.
If others like it, I'm not dismissing it.
we have a couple of newtypes over Text that do different kinds of
normalization. An IsString instance for these is useful
Thanks Etienne
When I tried to compile your Type.hs file, the first thing that broke was this:
class ((ma :: m a) = (f :: a - m b - Constraint)) (mb :: m b) | ma f - mb
You want the sort of 'm' to be BOX - BOX, but you can't do this at the moment.
As our paper say, the sort system is pretty
On April 25, 2012 04:15:41 Yitzchak Gale wrote:
The only reason I don't like using OverloadedStrings
for typing string literals as Text and ByteString
is that when you turn on OverloadedStrings, you turn
it on for all types, not just Text and ByteString.
I don't want to be forced to do that.
On Wed, Apr 25, 2012 at 8:19 AM, Tyson Whitehead twhiteh...@gmail.com wrote:
Is there a technical reason this couldn't be done? The Haskell report only
says doing this is not part of haskell. It doesn't say why.
I think the problem is incoherence, what if the same Map value got
used with two
From: Yitzchak Gale g...@sefer.org
Erik Hesselink wrote:
I don't think IsString should be dismissed so easily.
I'm just saying I don't want to be forced to use it.
If others like it, I'm not dismissing it.
we have a couple of newtypes over Text that do different kinds of
normalization.
The only reason I don't like using OverloadedStrings
for typing string literals as Text and ByteString
is that when you turn on OverloadedStrings, you turn
it on for all types, not just Text and ByteString.
I don't want to be forced to do that. Because
all other uses of OverloadedStrings
On Wed, Apr 25, 2012 at 11:39 AM, Ozgur Akgun ozgurak...@gmail.com wrote:
One can always use a Maybe to make an IsString literal total. Perhaps this
is what library authors should do in those cases when a fromString
implementation is obviously partial.
i.e. instead of instance IsString XML
Hi,
Am Mittwoch, den 25.04.2012, 11:15 +0300 schrieb Yitzchak Gale:
The only reason I don't like using OverloadedStrings
for typing string literals as Text and ByteString
is that when you turn on OverloadedStrings, you turn
it on for all types, not just Text and ByteString.
I don't want to
On April 25, 2012 12:20:16 Johan Tibell wrote:
On Wed, Apr 25, 2012 at 8:19 AM, Tyson Whitehead twhiteh...@gmail.com
wrote:
Is there a technical reason this couldn't be done? The Haskell report
only says doing this is not part of haskell. It doesn't say why.
I think the problem is
Hi,
Am Mittwoch, den 25.04.2012, 21:57 +0100 schrieb Joachim Breitner:
Am Mittwoch, den 25.04.2012, 11:15 +0300 schrieb Yitzchak Gale:
The only reason I don't like using OverloadedStrings
for typing string literals as Text and ByteString
is that when you turn on OverloadedStrings, you turn
18 matches
Mail list logo
