4 ms·
> Maybe I'm "holding it wrong" but this causes a lot of friction and lost time. It is a completely non-problem for functional code. It is a big problem for imp
by marcosdumay 5y ago
> Maybe I'm "holding it wrong" but this causes a lot of friction and lost time.
It is a completely non-problem for functional code. It is a big problem for imperative code.
You can't just write all of your code in a functional style, but depending on what you are doing the limit gets larger or smaller. So it's normal that this will be a showstopper for some people, and irrelevant to others.
- geokon 5y agoI don't really follow.. How is it a non problem in functional code? For instance you have some recursive idempotent function that blows at some point. Wouldn't you wanna see the state at which things broke? Just because things are functional doesn't mean you always knows the inputs at all times
- simiones 5y agoWhat does this have to do with imperative state? Take this program: compute x = 1 `div` (x - 3) map compute [1,2,3,4] Would seeing that it crashed in `compute` in `map` be enough info to debug, or finding out that `x` was 3 when it did also help? Edit: fixed to use integer division so we actually crash .