On Thu, Mar 22, 2012 at 6:49 AM, Ian Lynagh wrote:
>
> Hi all,
>
> Just a quick note to let you know about our release plans:
>
> We plan to put out a GHC 7.4.2 release candidate around the end of the
> March. The final release will probably not happen until around the end
> of April.
Looking for
On Thu, Mar 22, 2012 at 3:52 PM, Jan-Willem Maessen
wrote:
> Wait, I thought this is essentially what constructor specialization does? I
> suppose we might then keep around the old body. Or will these behave
> differently in the presence of, say, different constant Int arguments?
We do want to
I support a form of this in jhc by allowing specialization of values,
not just types.
It is actually the same mechanism as type specialization since that is
just value specialization where the value being specialized on is the
type parameter.
foo :: Bool -> Int
{-# SPECIALIZE foo True :: Int #-}
On Thu, Mar 22, 2012 at 5:09 PM, Johan Tibell wrote:
> Hi all,
>
> While looking at the GCC 4.7 [1] release notes I saw something that's
> perhaps worth stealing. Taken from the release notes:
>
>The inter-procedural constant propagation pass has been rewritten. It
>now performs generic fu
Hi all,
While looking at the GCC 4.7 [1] release notes I saw something that's
perhaps worth stealing. Taken from the release notes:
The inter-procedural constant propagation pass has been rewritten. It
now performs generic function specialization. For example when
compiling the follow
Hi all,
Just a quick note to let you know about our release plans:
We plan to put out a GHC 7.4.2 release candidate around the end of the
March. The final release will probably not happen until around the end
of April.
Thanks
Ian, on behalf of the GHC team
___
> >ghc --interactive now behaves different in regards to line numbers in
> >error messages than previous versions.
> >
> >They are now incremented with each evaluated expression.
> >
> > $ ghc --interactive -ignore-dot-ghci
> > Prelude> foo
> >
> > :2:1: Not in scope: `foo'
> > Pre
On 22 March 2012 12:13, Simon Marlow wrote:
> On 20/03/2012 20:12, Simon Hengel wrote:
>> They are now incremented with each evaluated expression.
Why *are* they incremented with each evaluation? Surely the only use
for line numbers would be in multi-line statements:
> :{
Prelude| do x <- [1..10
On 20/03/2012 20:12, Simon Hengel wrote:
Hi,
ghc --interactive now behaves different in regards to line numbers in
error messages than previous versions.
They are now incremented with each evaluated expression.
$ ghc --interactive -ignore-dot-ghci
Prelude> foo
:2:1: Not in scop
