I've just learned, via [some web site] that being strict will hamper Idris 2 significantly. Much as I like Haskell syntax, sometimes I think it would have been better to model Idris on something else...
-
-
Also, I can't resist adding that even in a total language it matters for performance reasons. Even if it is tempting to answer "Yes" to "is it lazy or strict?"
-
Sir, you are the academic. I'm the engineer. You should care about decidability and likewise stuff, heh.
- 2 more replies
New conversation -
-
-
I'd like to think of it this way: In 97% of all cases, laziness (+ a proper strictness analysis) will give you better performance when composing abstractions. The other 3% hide some nasty O(n) space/time increases that one has to carefully fix, which takes time and experience.
-
Is this a guess based on your own experience? I see statements like this a lot, and I'm sure people have good reasons for their own claims. I like both strict and lazy by default, depending what I'm doing. I really don't have a side here. But I did have to pick one for Idris.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.