Re:Escaping Hell with Monads (2017)
by pjmlp on Friday February 23, 2018 @10:10AM
(#16446712)
It is only a PITA to debug on paper, not when using a graphical debugger.
[ Parent
| on HN ]
Re:Escaping Hell with Monads (2017)
by seanmcdirmid on Friday February 23, 2018 @10:15AM
(#16446754)
How so? Visual studio still doesn’t reveal the right context when you actually find out the error has occurred.
Visual Studio isn't the only option.
https://blog.oz-code.com/debugging-linq-available-tool-compa...
Re:Escaping Hell with Monads (2017)
by seanmcdirmid on Friday February 23, 2018 @12:36PM
(#16447834)
Nice! Tooling is a large part of my trouble with FP, better tooling would make it easier to debug, especially those complex signal networks that require different debugging paradigms from imperative languages.
Re:Escaping Hell with Monads (2017)
by andrewprock on Friday February 23, 2018 @11:33AM
(#16447357)
This suggest that it's difficult to reason about the code. That's the last thing I want.