upgrade to elm 0.19

[erosson]

it's finally out~

https://github.com/elm/compiler/blob/master/upgrade-docs/0.19.md

[erosson]

pending dependency updates:

• [x] evancz/elm-markdown, for the changelog. workaround: parse in js (or wait? or reimplement?)
  • this is https://github.com/elm-explorations/markdown now!
• [x] NoRedInk/elm-decode-pipeline, for parsing gamedata json. workaround: use json.decode, without pipelining - I don't think we have anything beyond map8; no big deal
  • this moved: NoRedInk/elm-json-decode-pipeline
• [x] elm-community/maybe-extra. looks like they have a 0.19 branch, but it's unreleased - elm install can't find it, anyway. (list-extra/dict-extra are there.) likely resolved by waiting a bit, and if not, re-implementing unpack and unwrap solves 90% of our uses here
• [x] elm-lang/lazy - deprecated?! not good, dijkstra's currently depends on this for reasonable performance through memoization. impossible to reimplement - depends on side effects in elm's kernel code. we'll have to figure out another way to do this:
  • breadth-first on-demand, instead of dijkstra - response time/user experience is a bit slower with no preprocessing, but the code's much simpler, and uses less cpu overall.
  • Maybe instead of Lazy, preprocessing fills in the maybe, and if they click really fast (while it's still Nothing) we either ignore the click or run expensive dijkstra's twice
• [x] elm-community/linear-algebra and zaboco/elm-draggable - used for zooming/panning. blocker: re-implementing this without deps would be a lot of work. maybe I could fork, upgrade, temporarily publish in my own namespace, and send them a PR - if no other elm folks beat me to it - depends what deps they're waiting on, if any
  • moved to https://package.elm-lang.org/packages/elm-explorations/linear-algebra/latest, but no signs for elm-draggable
• [x] elm-live

[Judgy53]

Quickly checked if there was any updates :

• maybe-extra, looks like 0.19 branch has been merged and should now be installable.
• elm-draggable has been updated too.
• elm-live now supports 0.19.
• lazy , I've two lazy libs which are entirely written in elm, they might be worth looking at : eeue56/elm-lazy and eeue56/elm-lazy-list

[erosson]

Thanks!

Taking another shot at this now. elm-upgrade results:

---

SUCCESS! Your project's dependencies and code have been upgraded. However, your project may not yet compile due to API changes in your dependencies.

See https://github.com/elm/compiler/blob/master/upgrade-docs/0.19.md and the documentation for your dependencies for more information.

WARNING! 1 of your dependencies have not yet been upgraded to support Elm 0.19.

• https://github.com/elm-lang/lazy

Here are some common upgrade steps that you will need to do manually:

• NoRedInk/elm-json-decode-pipeline
  • [x] Changes uses of Json.Decode.Pipeline.decode to Json.Decode.succeed
• elm/core
  • [x] Replace uses of toString with String.fromInt, String.fromFloat, or Debug.toString as appropriate
• undefined
  • [x] Read the new documentation here: https://package.elm-lang.org/packages/elm/time/latest/
  • [x] Replace uses of Date and Time with Time.Posix
• elm/html
  • [x] If you used Html.program*, install elm/browser and switch to Browser.element or Browser.document
  • [x] If you used Html.beginnerProgram, install elm/browser and switch Browser.sandbox
• elm/browser
  • [x] Change code using Navigation.program* to use Browser.application
  • [x] Use the Browser.Key passed to your init function in any calls to Browser.Navigation.pushUrl/replaceUrl/back/forward
  • [x] Change code using Window.* to use Browser.Events.onResize
• elm/url
  • [x] Changes uses of Navigation.Location to Url.Url
  • [x] Change code using UrlParser. to use Url.Parser.

[erosson]

Upgraded. Known caveats:

• failing to parse game data may have some mangled error messages now
• clicking on several nodes really fast might be laggier than before (dijkstra may run twice for fast clicks)
  • a fake Lazy library was small enough to write myself, rather than use someone else's. double-evaluating sometimes is a consequence of not having 0.18's laziness side-effects. (It's not strictly unavoidable - could store the click and wait for preprocessing to finish to evaluate the click - not worth the trouble)
• 0.19 adds an --optimize flag for smaller/faster js builds. Using it requires removing all Debug calls, but I use lots of Debug calls. The goal here was just to get things running in 0.19; punting that optimization to #61.