core

> your definition of dead is elms definition of stability If Elm's definition of stability is keeping bugs and runtime errors for years, then I'm glad I stopped using Elm long ago. Not only were the issues unaddressed, but for the past years the PR got no human response. For instance this one¹ fixes infinite loops in the core. [¹]: https://github.com/elm/core/pull/1137

> It appears the last commits on GitHub are from mid 2024 That's not what I see. The last commits for elm/compiler were minor fixes in 2023. Last substantial changes were in 2021. See https://github.com/elm/compiler/commits/master/ The last commits for elm/core were in the first months of 2021. See https://github.com/elm/core/commits/master/ > It appears the main developer is working on a new thing? One of the problems is that the developer said several times, even in a recent interview, that he was still working on elm, with a focus on the long term. He gave a few vague hints about his private roadmap. After 4 years without any real public activity, I find it hard to believe there's some private activity.

elm is a lovely lang. it would be nice to have modern APIs on it. here's the project for new eyes: https://github.com/elm/core https://elm-lang.org/

You'll see people arguing that it's not, but I'll let you be the judge. https://elm-lang.org/news https://github.com/elm/compiler/pulse/monthly https://github.com/elm/core/pulse/monthly https://github.com/elm/compiler/commits/master https://github.com/elm/core/commits/master

As a use case other than the bottom type or "doesn't terminate", some pure languages use it to mean "this code path is impossible". I always liked the way Elm (and I assume many other pure functional languages) define(s) `Never`: type Never = JustOneMore Never As the only constructor takes an instance of itself as an argument, any attempt to construct one would become infinite. This very naturally allows for a function to obtain any value you want: never : Never -> a never (JustOneMore nvr) = never nvr If you can get a `Never` instance that can't possibly exist, you must be in a code path that can't happen, so you can get any value you want to short circuit early and make impossible return values. That makes it very useful in a language with no runtime exceptions to handle impossible cases. (E.g: you can go from a `Res

https://github.com/elm/core/blob/master/LICENSE It looks like an open source project. I don't get your point.

tail : List a -> Maybe (List a) Nice try though. https://github.com/elm/core/blob/master/src/List.elm#L548