Dear all,
We’ve been active since September making the Helium compiler more Haskell 2010
compliant.
In particular, we have a branch with support for Haskell 2010 type classes, a
branch that
supports import/export following the standard, and a branch that compiles to
LLVM instead
of the `old’ H
Hi Anthony,
We first go the slavish route, to provide a basis for changing things later.
So I am not looking for alternative ways of doing this, I am just wondering
whether there is a rationale for doing things this way.
The document does not give one.
And now I hear that records suffer from
Hello,
We are adding classes and instances to Helium.
We wondered about the aspect that it is allowed to have a class instance
of which not all fields have a piece of code/value associated with them, and
that as a result when you happen to call these, a run-time error results.
(see Sec. 4.3.2 o
I won’t be there. :-(
Jur
> On 26Aug, 2017, at 08:48, Carter Schonwald wrote:
>
> I'll be this time! :)
>
> We should coord a committee catch-up at icfp.
>
> Also I would like to propose we shift back to email based discussion. There's
> still the valid and important need of then taking the
://foswiki.cs.uu.nl/foswiki/Hage/WebHome where you can also
find a list of publications, many of which involve Haskell one way or another.
best,
Jurriaan Hage
Utrecht University
___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://mail.haskell.org/cgi-bin
