Closed abbradar closed 10 years ago
Sorry, I've misclicked.
Thanks!
One more thing: do you plan to release a new version with this soon? I ask because I have a friend to whom I'll need to explain why Haskell, too, has "scary segfaults" and help him fix his code later today. ^_^
I will push a new version to Hackage in a few moments. :)
Thanks!
New version released: http://hackage.haskell.org/package/matrix-0.3.1.0
My apologies for the misbehavior of these functions.
No problem, thanks for fast reaction! BTW, does Hackage need some time to build documentation? The links are inactive ATM.
Yes, documentation takes some time to appear. Not much since Hackage 2.
Hello, I had somewhat hard time debugging a code snippet from a friend that had caused a segfault in Haskell. I've used an old version of your library earlier where getElem was safe and reported out of bounds errors, and found its new behaviour only while looking through library code. Please, state in documentation that (!) and getElem is unsafe now or (I think this is better, because most users will expect that instead of segfaults, and that will clearly show unsafe code) make separate unsafeGetElem and make getElem and (!) throw errors on out of bounds, like earlier. Thanks!