Elixir v1.5.0-rc.0 released

Can not wait to use the Calendar improvements. Thanks!!

@josevalim in the ElixirConfEU you talked in your keynote about two interesting features: a Language Server implementation and a kind of Quickcheck support in tests. Are those features to be expected in future versions of the language? Or should we expect them to be developed as separated packages?

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

Wonderful! Thank you @whatyouhide

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?

@josevalim: I just updated:

1. asdf
2. asdf plugins: elixir and erlang
3. erlang to 20.0
4. elixir to 1.5.0-rc.0

and I have a problem:
I tried example call from changelog: Access.fetch(:foo, :bar), but result surprised me. I don’t see part about available function clauses.

Erlang/OTP 20 [erts-9.0] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:10] [hipe] [kernel-poll:false]

Interactive Elixir (1.5.0-rc.0) - press Ctrl+C to exit (type h() ENTER for help)
iex> Access.fetch(:foo, :bar)
** (FunctionClauseError) no function clause matching in Access.fetch/2    
    
    The following arguments were given to Access.fetch/2:
    
        # 1
        :foo
    
        # 2
        :bar
    
    (elixir) lib/access.ex:261: Access.fetch/2

I also want to ask same question as @svarlet.

Congratulations José and thank you.

On of my packages, ex_cldr, I’m seeing compilation and test times improve significantly - about twice the speed. This monster generates and runs over 12,000 tests so it makes a big difference!

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…

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.

Dude, everyone knows those systems will run nodejs… Node.js Is Bad Ass Rock Star Tech (Note: Despite what’s said in the video, Christopher Colombus did not discover that the world was round, everyone already knew that since like forever).

This limit was introduced to guard against a common error of a wrong unit - for example passing the number of nanoseconds, where milliseconds were expected.