Making Elm faster and friendlier in 0.16
elm-lang.org
Making Elm faster and friendlier in 0.16
1–10 of 92 posts
Re: Making Elm faster and friendlier in 0.16
#2Long anticipated, and now finally here :) I <3 the type diffs, exhaustiveness checks and TCO. Not completely sure about the removed syntax, but it's not like I used it a lot, so I guess simpler is better.
Re: Making Elm faster and friendlier in 0.16
#3Very nice. I love the "beginner hints" idea, and explicit enumeration of which cases are missing in incomplete pattern matches. Overall, the "compilers as assistants" idea seems great.
Re: Making Elm faster and friendlier in 0.16
#4Some of these errors remind me of Rust and the attempts in that community to give every error an exhaustive description [1].
This looks fantastic, and shows a true commitment to reducing friction with the language - a goal which often goes too long without attention.
Re: Making Elm faster and friendlier in 0.16
#5Elm is such a pleasure to learn. I really need to sit down and write something non-trivial with it one of these days.
Re: Making Elm faster and friendlier in 0.16
#6Elm is a beautiful expression of a language. Alone, it is a work of art. Put to use, it lets you build works of art. One of the best contributions to modern languages.
Re: Making Elm faster and friendlier in 0.16
#7Finally TCO!
Actually in my UI-heavy Elm programs it isn't that often that I have to write functions with large recursion depth. But it is really comforting to know that the compiler is analyzing my code and making it more efficient. :)
Re: Making Elm faster and friendlier in 0.16
#8I'm just finishing up a first-year course at McMaster University where we learned basic CS concepts (divide and conquer, state machines, recursion, algebraic data types, FRP, etc) using ELM. It's the first time I've ever put an honest effort into learning a pure functional language, and although it was initially frustrating to a self-taught programmer with a background in several procedural languages and SQL, it's growing on me, and I'm probably going to look for a side project (maybe a small game or a simple CPU simulator) to build with ELM when the course is over.
I only wish the "Improved error messages" and "Catching more bugs" features had been introduced about three months ago, probably would have saved me hours!
Re: Making Elm faster and friendlier in 0.16
#9Some of these errors remind me of Rust and the attempts in that community to give every error an exhaustive description [1]. This looks fantastic, and shows a true commitment to reducing friction with the language - a goal which often goes too long without attention. [1]: https://github.com/rust-lang/rust/issues/24407
Yup, I would strongly agree. Diagnostics are one of those things that's easy to let slip by the wayside, but we've seen a huge payoff for users with all the time we've invested in ours. Glad to see other languages like Elm help raise the bar here too.
Re: Making Elm faster and friendlier in 0.16
#10I wish the clojure compiler also had the explicit goal of making things easier like this...