Elixir
Elixir Core Team
1. Bug fixes
Elixir
- [bin/elixir] Properly handle the
--dbgflag in Elixir’s CLI - [Code.Formatter] Add brackets around keyword lists when formatting the left-hand side of
when - [Kernel] Only infer size in pinned variable in binary strings when needed
- [System] Add a note that arguments are unsafe when invoking .bat/.com scripts on Windows via
System.cmd/3 - [Port] Add a note that arguments are unsafe when invoking .bat/.com scripts on Windows
- [URI] Ensure
:undefinedfields are properly converted tonilwhen invoking Erlang’s API
Logger
- [Logger] Ensure translators are persisted across logger restarts
Mix
- [mix compile] Ensure compile paths are accessible during compilation
Trending in News
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming











Showing Posts 4 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
restlessronin
josevalim
Erlang guarantees byte code compatibility across 3 versions. So we can’t provide precompiled Rebar and Hex that works from 24 all the way up to 27 (sometimes we can, but not this time). The fix would be to precompile several versions of them, we want to do for future releases.
sabiwara
Unfortunately the answer is no.
mainis the future 1.17, which will be the first version to support OTP27. You can check the compatibility matrix here.I don’t recall exactly the issue, but 1.16 can’t support both OTP24 and OTP27 at the same time, so we first have to wait for 1.17 which drops OTP24 support.
Eiji
Oh, I was thinking that next patch release would contain minimum changes for
Erlang 27support. So far I have installedref:mainusingasdfand all tests have passed, so it shouldn’t be hard, right? Is it planned forv1.16.4?