RE: unsafePtrEq in 5.03?

2002-04-18 Thread Simon Marlow
Elliott Cc: Ghc-Bugs Subject: Re: unsafePtrEq in 5.03? A spot of CVS archeology revealed that it was removed as a primop as part of a NCG overhaul couple of months ago. Don't know if leaving it out was simply an omission or if there's something deeper going on. Anyway, you can approximate

RE: unsafePtrEq in 5.03?

2002-04-18 Thread Conal Elliott
unsafePtrEq :: a - a - Bool unsafePtrEq a b = (unsafeCoerce# a) `eqAddr#` (unsafeCoerce# b) which is fine by me. - Conal -Original Message- From: Simon Marlow Sent: Thursday, April 18, 2002 4:29 AM To: Sigbjorn Finne; Conal Elliott Cc: Ghc-Bugs Subject: RE: unsafePtrEq in 5.03? Conal

unsafePtrEq in 5.03?

2002-04-16 Thread Conal Elliott
Did unsafePtrEq disappear between 5.02 and 5.03? - Conal

Re: unsafePtrEq in 5.03?

2002-04-16 Thread Sigbjorn Finne
GHC.Base unsafePtrEq :: a - a - Bool unsafePtrEq a b = (unsafeCoerce# a) `eqAddr#` (unsafeCoerce# b) Clearly, it doesn't chase indirections. hth --sigbjorn - Original Message - From: Conal Elliott To: Ghc-Bugs Sent: Tuesday, April 16, 2002 18:43 Subject: unsafePtrEq in 5.03? Did