Keep discussion on Discourse and Slack. Please do not post on HN, reddit, twitter, etc.
I am hoping to get some feedback on
The goal of 0.19.1 is generally to clean up the rough edges introduced in 0.19.0 such that we have a really solid foundation for newcomers, professionals, scientists, etc.
The goal of the BETA is to get some of the more engaged community members to try it out and find any problems before a real release that’ll go out to a broader audience. I do not recommend switching your company to using the BETA. Wait for the real release! Only try out the BETA if you want to help test it out.
Notable improvements include:
- Parse error message quality (like this and this)
- Faster compilation, especially for incremental compiles
- Uses filelocks so that cached files are not corrupted when plugins run
elm makemultiple times on the same project at the same time. (Still worth avoiding that though!)
- More intuitive multiline declarations in REPL
- Various bug fixes
There are no language changes, so once you swap the
"elm-version" in your
elm.json, most users should be able to proceed without any further code changes. You may run into a handful of bugfixes though! I will outline them in the next comment in this thread!
Say you want to try
elm-0.19.1-beta-1 on your
~/Documents/hats/ project. Download the binary from the following links to
~/Documents/hats/elm and run
./elm make to try it out. No need to change your
While I do highly appreciate people trying these out and helping with the goals listed below, I do not recommend using these in production! They have specific limitations (e.g.
elm publish is disabled for now) and may have problems that we have not figured out yet.
In this testing period, I am hoping to get help on the following topics:
Check bug fixes. A couple things started going wrong in 0.19.0, like
x /= 0,
type Height = Height Floatin
--optimize, etc. If you experienced any of these, please check that it is resolved with the new binary and report back!
Time compiler with 50k+ LOC projects. The new binaries should be a decent bit faster and should take advantage of multiple cores better. I am hoping to hear some before-and-after numbers just to confirm that this is the case.
Cause parse errors. Please try to cause parse errors and let us know if you find something interesting. Maybe there is a message that seems off or not helpful enough. That kind of thing.
Try out the REPL. It should be more intuitive to make multi-line expressions. Try it out and report back how it feels.
To report anything that may need changes, please create an SSCCE and report your findings in this thread on discourse or in the #core-coordination channel on slack.
Note: There is some supporting tooling that is not compatible yet. This is okay! The point of this time is so that people can get prepared without a bunch of people telling them to hurry up. For example, a bit more work is needed on
elm-test, and I’m sure there are editors with fancy features that are not updated yet. This is all as expected! This is part of why I do not recommend switching to the BETA at work.
Thank you to anyone who gives the BETA a try, and please keep discussion on discourse and slack. There may still be problems, so I’d like to do more testing before this reaches a broader audience through HN, reddit, twitter, etc. I’ll make a post on
elm-lang.org and share it on twitter when it is ready for a broader release like that!
And thank you to the folks who helped test the ALPHA. Very glad to find those issues early!