Hello everyone,
Elixir v0.14.3 will be released this weekend.
The major changes are:
defstruct
no longer creates a type, support for %Struct{...}
syntax in typespecs have been added instead<<x :: [little, utf16]>>
), -
should be used as the separator instead (as in <<x :: little-utf16>>
)See the changelog for a full list of changes.
We are approaching 1.0 and have no more backwards incompatible changes left in the issue tracker, this release is hopefully the last one with breaking changes. For the next release, 0.15, we want to finish the logger that will print all errors in Elixir terms. After 0.15 is out of the door we can start with the release candidates for 1.0
Can I ask about this change:
exit(integer)
is no longer supported from scripts to configure the exit signal. Use exit({:shutdown, integer})
insteadThe @doc for exit doesn’t mention this, and exit(1)
still works. Does this apply only in some circumstances?
Dave
--
You received this message because you are subscribed to the Google Groups "elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-co...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
<<x :: [little, utf16]>>
), -
should be used as the separator instead (as in <<x :: little-utf16>>
)--
You received this message because you are subscribed to the Google Groups "elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-co...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
- Using a list for bitstring modifiers have been deprecated (as in
<<x :: [little, utf16]>>
),-
should be used as the separator instead (as in<<x :: little-utf16>>
)
Does this mean one can no longer use macros in bitstring modifiers? I remember some of my libraries used that to avoid long, repeating modifiers all across the project.