4 ms·
> So I'm mostly trading time spend debugging subtle state errors with fixing compile type errors. It feels not as productive, since I'm usually looking at error
by naasking 11y ago
> So I'm mostly trading time spend debugging subtle state errors with fixing compile type errors. It feels not as productive, since I'm usually looking at errors.
Strange, because debugging subtle state errors seems far more time consuming to me than fixing compile-time errors. You have to launch debugging sessions or insert logging commands and step through reams of code, where compile-time errors tell you exactly where the problems are.
- iamwil 11y agoYeah, it's true. Logically, I know it's better to catch it all at compile time. But it just feels things are broken all the time, since I don't get to watch my program run nearly as much as I use to. However, when it runs, it usually does work. I think I'm just not as use to structuring my programs in FP yet.
- garfieldnate 11y agoI had trouble because the compiler errors were very hard to understand. If your code compiles then yeah, you can step through it. If your code does not compile and you don't understand what the problem is, then you're stuck. This makes me think it would be interesting to have a step-through compiler. I don't know if that even makes sense, but it sounds helpful.
- naasking 11y agoHaskell has the option to run your code without type checking [1], so this isn't an inherent limitation to type checking. [1] https://downloads.haskell.org/~ghc/latest/docs/html/users_guide/defer-type-errors.html https://downloads.haskell.org/~ghc/latest/docs/html/users_gu...