Fuck, I've recently realized that Haskell can't even support the definition of an array. It only does this by foreign interfacing with C, with things like foreign import ccall unsafe "memcpy"
memcpy_ba_ptr :: MutableByteArray# RealWorld -> Ptr a -> CSize -> IO (Ptr ())
(taken from the source of "array" from Hackage)
Please forgive me for all my posts on this forum where I've defended Haskell as if it's a good language. Unfortunately, despite its good type system and syntax it's just ab absolutely impractical and immature shitpile of a language.
>>3
Oh yeah, forced gonads suck too. They're just useless hassle because half the real Haskell code uses foreign calls and unsafePerformIO anyway.
Name:
Anonymous2014-02-18 14:41
calling out to C is one of the most important things a high level language not based on the JVM needs to do. literally everyone except you agrees calling out to C is a useful and necessary feature.
you are literally complaining that the STANDARD LIBRARY uses an efficient implementation of arrays. christ you are dumb. wait til you find out how languages implement high performance math/science libraries
>>5 calling out to C is one of the most important things a high level language not based on the JVM needs to do.
Since JNI exists, that statement even applies to JVM languages.