Personally I have not felt the need to use the debugger very often. As the compiler signals most of the errors, once your program compiles, it usually does what you've programmed it to do. So most problems that occur at that point have to do with mistakes in programming logic. Going through my code, which the Elm architecture makes very easy, is usually enough to spot them.
Can anyone give (concrete) examples wherein the debugger proved to be useful, even crucial, in resolving the problem or bug? -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
