The situation should be much improved now in 0.18. I don't see it mentioned in the release notes, but from the beta announcement <https://gist.github.com/evancz/8032a3ac6eb7a4ac8e0956ed6d386798>:
Fix elm-make bug where build artifacts could get corrupted, requiring > delete of elm-stuff/build-artifacts/ > But it appears that we still need to delete elm-stuff sometimes. So it's probably a workaround for more than one bug. Anthony, the situation you describe sounds like it must be related to elm-package. If you can reproduce your problem and there isn't already a relevant bug report <https://github.com/elm-lang/elm-package/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen>, I would recommend opening one! On Mon, Nov 28, 2016 at 10:02 AM, Rex van der Spuy <[email protected]> wrote: > > I'm assuming this should actually never happen. >> > > Yes, "have you tried deleting elm-stuff?" is a bit of oral tradition > folklore that can magically cure all manner of ailments. > It's Elm's take on "Have you tried turning it off and on again?" > It burned me as a beginner too, and has been a problem since I started > using Elm with 0.15 > > Does anyone know if it's possible to prevent this from being necessary? > Or is there a technical reason why the complier can't forcibly clear the > elm-stuff cache? > > -- > 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. > -- 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.
