Ext-core is not a library; spitting it out and sucking it in is an integral
part of GHC.
That said, I think there may be a library for processing the ext-core code
itself (parsing, typechecking etc). I don't think Aaron is working on that.
Also, what you need for your PhD is the spitting-out p
Well, the work I'm doing on it right now includes modifying it to
work with System FC, which means it won't work with 6.6.
Aaron
On Apr 17, 2007, at 10:54 AM, Neil Mitchell wrote:
Hi
> >Release plans:
> >- get external core working again
>
> Can't this happen entirely separate from any GHC
It is still coming along! :)
I'm frustrated with how slowly I've been progressing with it (even
though I do have good reasons), but I'm not stopping, and I believe
it will be ready for 6.8.
Knowing that you're waiting for it definitely gives me some
motivation to push harder on it. I'm gl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Lynagh wrote:
> On Tue, Apr 03, 2007 at 03:13:50PM +, C Rodrigues wrote:
>> The wiki has "edit" links if I login as guest, but not if I login as
>> heatsink.
>
> Should be fixed now.
>
>> Is that also because of the spam issue?
>
> Yup; you
Hi
> >Release plans:
> >- get external core working again
>
> Can't this happen entirely separate from any GHC releases?
It will work in the HEAD as soon as it's done, but it won't be in a
released compiler until the release after that.
AFAIWA the library in the past was entirely stand alone,
What are the plans for the esc branch?
Are the changing going to be merged?
Rene.
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
On Tue, Apr 17, 2007 at 06:15:49PM +0100, Neil Mitchell wrote:
>
> >Release plans:
> >- get external core working again
>
> Can't this happen entirely separate from any GHC releases?
It will work in the HEAD as soon as it's done, but it won't be in a
released compiler until the release after tha
Hi
Release plans:
- get external core working again
Can't this happen entirely separate from any GHC releases? From what
I've heard people were thinking of wrapping this up in the next few
months. I personally need this to make my PhD work on more than just
Yhc :-)
Thanks
Neil
__
| Yes, but where is it written that what cannot be expressed in system-
| F is type incorrect? We think it is still type safe, and it is an
| extrcat of a larger program that is quite useful (if we managed to
| compile it),
Indeed! Well-typed programs don't go wrong, but not every program that n
On Apr 17, 2007, at 2:57 PM, Simon Peyton-Jones wrote:
| Just to show what kind of problems we are currently facing. The
| following type checks in our EHC compiler and in Hugs, but not in
the
| GHC:
|
| module Test where
|
| data T s = forall x. T (s -> (x -> s) -> (x, s, Int))
|
| run :: (
| Just to show what kind of problems we are currently facing. The
| following type checks in our EHC compiler and in Hugs, but not in the
| GHC:
|
| module Test where
|
| data T s = forall x. T (s -> (x -> s) -> (x, s, Int))
|
| run :: (forall s . T s) -> Int
| run ts = case ts of
| T
Doaitse Swierstra wrote:
> Just to show what kind of problems we are currently facing. The
> following type checks in our EHC compiler and in Hugs, but not in the GHC:
>
> module Test where
>
> data T s = forall x. T (s -> (x -> s) -> (x, s, Int))
>
> run :: (forall s . T s) -> Int
> run ts =
Just to show what kind of problems we are currently facing. The
following type checks in our EHC compiler and in Hugs, but not in the
GHC:
module Test where
data T s = forall x. T (s -> (x -> s) -> (x, s, Int))
run :: (forall s . T s) -> Int
run ts = case ts of
T g -> let (x,_,
| > - left-to-right impredicative instantiation: runST $ foo
|
| This concerns me. With each ad-hoc extension of the type system, I
| worry that soon the GHC type system will become so byzantine and
| ill-specified that the type checker can only be cloned, not
| substantially improved on
On this
Isaac Dupree wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Marlow wrote:
Thanks for letting me know about the email rejection.
Cheers,
Simon
I got the same when trying to report a bug in alex - did that report get
through to you, or should I send it again? On the other hand,
Stefan O'Rear wrote:
What do you think of this plan? Are there features/bug-fixes that you
really want to see in 6.8?
Good code generation for loops. I understand they are rare in
practice, but it's kinda disheartening to write memset() and see in
the asm loop 11 memory references, 9 to the
Alfonso Acosta wrote:
On 4/16/07, Simon Marlow <[EMAIL PROTECTED]> wrote:
Are there features/bug-fixes that you really
want to see in 6.8?
How about dynamic libraries? (there are a few 6.8 tickets for that I think)
I'm not sure if this will be ready for 6.8, but of course if it is then it'll
Go here:
http://hackage.haskell.org/trac/ghc/roadmap
and click on the active tickets for 6.6.2
Simon
| -Original Message-
| From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
| Behalf Of David Roundy
| Sent: 16 April 2007 18:01
| To: glasgow-haskell-users@haskell.org
| Subject:
18 matches
Mail list logo
