We will see how things evolve. Property testing (which remember, is for data only for now, not for state machines stuff like Quviq’s QuickCheck) might land in ExUnit in future versions of Elixir. The language Server Protocol implementation is likely to remain a separate package. We’ll see how it goes

@ericmj, @michalmuskala just fixed asdf-elixir so it’s now possible for it to install versions like: 1.5.0-rc.0-otp-20, binaries will now be downloaded from repo.hex.pm as shown on bob's README. Thanks for your reporting this issue.

This is a tricky one. Exception.blame/3 works only on modules compiled on OTP 20. Most package managers use the precompiled Elixir which is compiled on the lowest supported release - currently OTP 18. This means when you use precompiled Elixir, you won’t get nice diffing from stdlib modules (but you would in your own modules or packages since you compile them every time).

This is understandably inconvenient. Hopefully, there will be a solution before the final release.

I just checked the changelog and I’m a bit surprised by this one:

[Enum] Deprecate Enum.filter_map/3 in favor of Enum.filter/2 + Enum.map/2 or for-comprehensions

I assume that we would now have to filter |> map instead ? If this produces the same result it does not have the same algorithmic complexity. Why is it now deprecated?

Looking forward to the new Date functions, as well as the async_stream timeout option Although it’s sad to see the filter_map function go…

Only thing that worries me, though:

[Calendar] Limit Calendar.ISO up to year 10000

I’d put a TODO note for future developers to revise that in a few thousand years — we don’t want to cause a bug that could bring down the life support systems in planets across the galaxy…