Re: [Haskell-cafe] Re: Profiling nested case

2008-07-24 Thread Ryan Ingram
Done. http://hackage.haskell.org/trac/ghc/ticket/2465 -- ryan On 7/23/08, Simon Peyton-Jones <[EMAIL PROTECTED]> wrote: > | I had similar experiences as you when attempting to write "high > | performance Haskell"; the language makes you want to use high-level > | abstracted functions but the o

RE: [Haskell-cafe] Re: Profiling nested case

2008-07-23 Thread Simon Peyton-Jones
| I had similar experiences as you when attempting to write "high | performance Haskell"; the language makes you want to use high-level | abstracted functions but the optimizer (while amazing, to be honest) | seems to miss a few cases that it seems like it should hit. Ryan, if you find any of thes

Re: [Haskell-cafe] Re: Profiling nested case

2008-07-21 Thread Ryan Ingram
I had similar experiences as you when attempting to write "high performance Haskell"; the language makes you want to use high-level abstracted functions but the optimizer (while amazing, to be honest) seems to miss a few cases that it seems like it should hit. The problem seems to be that the comp

[Haskell-cafe] Re: Profiling nested case

2008-07-19 Thread Mitar
Hi! I had to change code somewhat. Now I have a function like: worldScene point = case redSphere (0,50,0) 50 point of v@(Right _) -> v Left d1 -> case greenSphere (25,-250,0) 50 point of v@(Right _) -> v Left d2 -> Left $ d1 `min` d2 (Of course there could be more objects.) Any sugg

Re: [Haskell-cafe] Re: Profiling nested case

2008-07-18 Thread Don Stewart
ben.franksen: > Mitar wrote: > > On Fri, Jul 18, 2008 at 3:54 PM, Chaddaï Fouché > > <[EMAIL PROTECTED]> wrote: > >>> So that I can easily change the type everywhere. But it would be much > >>> nicer to write: > >>> > >>> data Quaternion a = Q !a !a !a !a deriving (Eq,Show) > >>> > >>> Only the per

[Haskell-cafe] Re: Profiling nested case

2008-07-18 Thread Ben Franksen
Mitar wrote: > On Fri, Jul 18, 2008 at 3:54 PM, Chaddaï Fouché > <[EMAIL PROTECTED]> wrote: >>> So that I can easily change the type everywhere. But it would be much >>> nicer to write: >>> >>> data Quaternion a = Q !a !a !a !a deriving (Eq,Show) >>> >>> Only the performance of Num instance functio