3 ms·
It's not "unpredictable" as in "stochastic", but rather as in "hard to reason about". This may be compiler-specific. Say, Haskell does not give you much heads-
by nine_k 4y ago
It's not "unpredictable" as in "stochastic", but rather as in "hard to reason about".
This may be compiler-specific. Say, Haskell does not give you much heads-up on laziness: whether stream fusion actually kicks in where you expect it to, or are you encountering quadratic behavior due to laziness [1].
If Ferret dives you decent visibility into issues like these, laziness may be usable even in hard-realtime setting, because it would become obvious and predictable for the developer.
[1]: https://accidentallyquadratic.tumblr.com/post/114149142587/revisiting-haskell-network-http https://accidentallyquadratic.tumblr.com/post/114149142587/r...
- dllthomas 4y ago> whether stream fusion actually kicks in where you expect it to An aside, but I remembered seeing something that let you test for that, likely https://hackage.haskell.org/package/inspection-testing https://hackage.haskell.org/package/inspection-testing