I linked to the relevant timestamp, that section is only a few minutes 
hkrutzer
hkrutzer
I have also encountered this pattern. (and, I have to say, many cases where the type system detected dead code and incorrect parameters)
1
itzmidinesh
Amazing! I am very happy to see the steady progress on the type system. Looking forward to trying it out soon.
1
zachdaniel
Creator of Ash
andyleclair
I am quite literally hooting and hollering at my desk as I watch the typechecker find bugs in ancient parts of my work codebase. So excited for this release!
9
delitrem
To be brief. When compiler or something else generates the exactly same output (up to bit) or has exactly the same behaviour on various environments, machines, etc.
Some time ago I have found and fixed bugs in Erlang (and also in rebar3 and LFE) related to non-deterministic behaviour, it’s thanks to Guix System which uses only deterministic package builds. If something is not deterministic, it will yell you about it.
And well, if I remember correctly, with sources stripped from compiled files, LSP’s feature jump to definition will not work, at least with current realizations.
2
Eiji
Related issue:
https://github.com/elixir-lang/elixir/issues/13975
Previously for such code:
defmodule Example do
if false do
alias Date, as: D
def sample, do: D.utc_today()
end
end
we’ve got the unused alias warning, because the alias was created, but also never expanded since the if condition always fail.
6
castagnag
cmo
It’s worth upgrading, running mix compile to see if you have any type errors, and then downgrading back to whatever you’re on if you don’t want to run an RC in production.
5
lud
Charlists as sigils - formats charlists as
~csigils, for example'foo'becomes~c"foo"
This is already the case with Elixir 1.17, and IIRC it’s the case since that sigil was introduced.
So does it mean that now the command will do so only if the option is provided?
2