If you use INLINEABLE, that should make the function specialisable to a
particular monad, even if it's in a different module. You shouldn't need INLINE
for that.
I don't understand the difference between cases (2) and (3).
I am still suspicious of why there are so many calls to this one
Ah yes! A palpable bug thank you. Fixing..
S
| -Original Message-
| From: Herbert Valerio Riedel [mailto:hvrie...@gmail.com]
| Sent: 17 December 2014 10:01
| To: Simon Peyton Jones
| Cc: Edward Kmett; Austin Seipp
| Subject: Re: type-checker regression in GHC HEAD?
|
| Hello
By unsubstantiated guess is that INLINEABLE would have the same effect as
INLINE here, as GHC doesn't see fit to actually inline the function, even with
INLINE -- the big improvement seen between (1) and (2) is actually
specialization, not inlining. The jump from (2) to (3) is actual inlining.
I still would like to understand why INLINE does not make it inline. That's
weird.
Eg way to reproduce.
Simion
| -Original Message-
| From: Richard Eisenberg [mailto:e...@cis.upenn.edu]
| Sent: 17 December 2014 15:56
| To: Simon Peyton Jones
| Cc: Joachim Breitner;
Austin, you may want to say when 7.8.4 will come out.
Simon
| -Original Message-
| From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of
| Austin Seipp
| Sent: 16 December 2014 21:11
| To: ghc-devs@haskell.org
| Subject: GHC Weekly News - 2014/12/16
|
| Hi *, time
Is it possible INLINE didn't inline the function because it's recursive? If
it were my function, I'd probably try a manual worker /wrapper.
On 07:59, Wed, Dec 17, 2014 Simon Peyton Jones simo...@microsoft.com
wrote:
I still would like to understand why INLINE does not make it inline.
That's
On 2014-12-16 at 22:45:36 +0100, Richard Eisenberg wrote:
I've learned several very interesting things in this analysis.
- Inlining polymorphic methods is very important.
otoh, there are cases where marking methods INLINE have catastrophic
effects; the following
I'm implementing Template Haskell support for injective type families and I'm
struggling to
understand DsMeta module. It seems that all functions in that module delegate
their calls to
functions in Language.Haskell.TH.Lib via wired-in names and the `DsMeta.rep2`
function. I'm
puzzled by this
On Dec 17, 2014, at 12:29 PM, Jan Stolarek jan.stola...@p.lodz.pl wrote:
Why not implement repPlainTV like this: ?
repPlainTV :: Core TH.Name - DsM (Core TH.TyVarBndr)
repPlainTV (MkC nm) = return $ MkC (TH.PlainTV nm)
In short, that's ill typed. We have
newtype Core a = MkC CoreExpr
Thanks. That helps but I still don't understand why the calls are delegated to
template-haskell
library. Couldn't all of this be done locally?
Janek
Dnia środa, 17 grudnia 2014, Richard Eisenberg napisał:
On Dec 17, 2014, at 12:29 PM, Jan Stolarek jan.stola...@p.lodz.pl wrote:
Why not
But you need an expression that, say, produces a PlainTV. Where are you going
to find an expression that does this without using the template-haskell library?
On Dec 17, 2014, at 2:33 PM, Jan Stolarek jan.stola...@p.lodz.pl wrote:
Thanks. That helps but I still don't understand why the calls
Hi *,
Everyone has been working hard getting things ready for the branch/RC
later this week - and that's really appreciated! As always, GHC
wouldn't be what it is without you.
But it's the holidays - that's stressful for some, and real time
consuming for others. So to keep things light and a
Hey all,
I was trying to define some pattern synonyms in ghci recently, and that
doesnt seem to work. Is that something slated to be fix in 7.10 or
something?
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
13 matches
Mail list logo
