Re: [Haskell] Question for the haskell implementors: Arrays, unsafePerformIO, runST

2006-02-16 Thread Jan-Willem Maessen
On Feb 15, 2006, at 10:53 PM, John Meacham wrote: So, I finally decided that jhc needs real arrays, but am running into an issue and was wondering how other compilers solve it, or if there is a general accepted way to do so. ... now, the problem occurs in newAT__ newAT__ :: Int -> AT a -> A

Re: [Haskell] Question for the haskell implementors: Arrays, unsafePerformIO, runST

2006-02-15 Thread Taral
On 2/15/06, John Meacham <[EMAIL PROTECTED]> wrote: > > foreign import primitive "prim_newWorld__" :: forall a . a -> World__ > > which will throw away its argument and produce a World__. but since it > is primtive, the compiler will assume the world it returns might depend > on its argument. then

[Haskell] Question for the haskell implementors: Arrays, unsafePerformIO, runST

2006-02-15 Thread John Meacham
So, I finally decided that jhc needs real arrays, but am running into an issue and was wondering how other compilers solve it, or if there is a general accepted way to do so. here is what I have so far > -- The opaque internal array type > data Array__ a > > -- the array transformer quasi-monad >