-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Erlang/OTP 25 new features #11220
Comments
Erlang 25 will also support reconfiguration of |
Do you want a separate issue for compiling with OTP 25? This is from GitHub CI, and I tried clearing the CI cache, but it may be related to a NIF?
|
You are using a precompiled Elixir version. It is just a matter of time until we have precompiled versions for OTP 25. It is usually tackled automatically by build tools. You can also compile it yourself. |
Thanks. I've opened an issue with |
I noticed there were also changes to the |
Our goal is to use the task API for that. We will see how it will go once we support it in OTP 24. |
Note for reference: erlang/otp pull request 'compiler: Start all potential nif functions with a nif_start #6193', merged on erlang/otp:master the pull request change the way attribute
|
Would it make sense to add support for the I believe it would be fine to always emit it as a persisted attribute - it would be just ignored on older OTP releases. I had to do some ugly hacks to get the support in the current version https://github.com/spawnfest/json_native/blob/main/lib/jason_native.ex#L10-L13 |
Yes, we can definitely support it. A PR is welcome! |
I looked into this a bit. It's not particularly complicated, but we do need to port validation rules from |
I'm wondering why the following task requires "OTP 25 exclusively"? Afaik the functionality had been in OTP since 23.
|
I don't remember the details but I tried to add it on main and ran into issues for the RPC case. The rest of the support is already in and you can use undefined in |
Next Elixir version will depend on OTP 25+26+27, so we can start tackling this one. |
To be implemented when Erlang 25 is released:
-nifs
To be implemented when we require Erlang 25 exclusively:
-start_epmd false -erl_epmd_port 6789
on both vm.args/remote.vm.args if you need epmdless:erlang.float_to_binary([:short])
inFloat.to_string/1
instead of private APIformat_status/1
callback for GenServercalling_self
clause inGenServer.call
as that is now in Erlang/OTPPlease do not send PRs for those, as it will take a while until we can effectively accept them.
The text was updated successfully, but these errors were encountered: