Elixir
Elixir v1.17.0-rc.1 released
1. Enhancements
Elixir
- [Duration] Add
Duration.to_iso8601/1andDuration.from_iso8601/1 - [Keyword] Add
Keyword.intersect/2-3to mirror theMapAPI
Mix
- [mix profile.tprof] Add a new profiler, available on Erlang/OTP 27+, which can measure count, time, and heap usage
- [mix test] Generate cover HTML files in parallel
2. Bug fixes
Elixir
- [Kernel] Avoid double tracing events when capturing a function
- [Kernel] Fix a bug where captured arguments would conflict when a capture included a macro that also used captures
3. Soft deprecations
Mix
- [mix profile.cprof] Deprecated in favor of the new
mix profile.tprof - [mix profile.eprof] Deprecated in favor of the new
mix profile.tprof
Most Liked
josevalim
Everyone, please give this a try. It should be the last stop before v1.17.0 final.
josevalim
It is not an Elixir bug. Because of meta-programming, the code is effectively part of your app, Elixir cannot know otherwise (unless the code was annotated - which wasn’t and then it requires a library patch anyway). ![]()
Warnings that arises when compiling deps (not your code), does not cause --warnings-as-errors to fail.
josevalim
That’s a bug in the iso8601 package. Check out it issues tracker.
dfalling
It’s already been patched (but not yet released) in Absinthe thanks to @doughsay in #1318. But this didn’t previously cause --warnings-as-errors to fail before. It was suggested by sabiwara that maybe this is caused by metaprogramming.
This is the only lib in my codebase that was adversely affected by 1.17. Should I report a ticket in Elixir as well?







