Yep, coincidence that lined up with our 1.20 update. Sorry for the false alarm!
neilberkman
lud
sergio
Very grateful for all of the hard work. I love working with Elixir so much, arguably the nicest part of my job for real. Since 2016, it has been a lovely language and platform to work in. It’s only getting better. 
4
type1fool
Bravo!
I can’t wait to update some projects and find out what typing violations are raised.
Anonymous functions within
defmodulecan have only up to 20 arguments.
If this is an issue, you can use maps or tuples to group the data.
Note the functions themselves insidedefmodule, such as the ones defined
insidedefand friends, can still have up to 255 arguments.
Here I thought 6 args was excessive. 
[mix source] Add
mix source MODULEto print or open a given module/function location
This will be useful for agent prompts where you use the module name. Less grepping is nice.
1
FlyingNoodle
matt-savvy
Keep in mind that the compiler doesn’t check types on functions, behaviours, protocols, or struct fields. IMO this is where Dialyzer still can provide value, by catching things that the type system can’t yet.
4
josevalim
Creator of Elixir
Sorry, the slides could be clearer. We definitely infer and check functions and protocols, but you can’t define signature for functions and behaviours, so Dialyzer is ahead there.
3
emptytuple
Nezteb
Fun fact, this combines with other flags nicely! e.g. mix test ––warnings-as-errors ––dry–run
Thank you @josevalim for patiently working through the PR with me!
0
Awlexus
Hi, I encountered an issue with a warning:
warning: comparison between distinct types found:
item == :only
given types:
dynamic(%{..., number: term(), type: binary()}) == :only
where "item" was given the types:
# type: dynamic(%{..., type: term()})
# from: lib/themes/theme_name.ex:5:24
item.type == "previous"
# type: dynamic(%{..., type: binary()})
# from: lib/themes/theme_name.ex:17:24
item.type == "page"
# type: dynamic(%{..., number: term(), type: binary()})
# from: lib/themes/theme_name.ex:19:30
item.number == assigns.current_page
While Elixir can compare across all types, you are comparing across types which are always disjoint, and the result is either always true or always false
type warning found at:
│
23 │ <.link
│ ~~~~~~
│
└─ (themes 1.2.0-11) lib/themes/theme_name.ex:23: Themes.ThemeName."pagination (overridable 1)"/1
The content of the warning is correct, but it is referencing the wrong file. Themes.ThemeName embeds a few components using embed_templates("theme_name/*") (Phoenix.Component.embed_templates/2) and the actual problem in this case is in lib/themes/theme_name/pagination.html.heex.
I’m writing this here, because I’m not sure if this is an issue in Phoenix Liveview or Elixir 1.20. I took a quick look at the issues for both repos, but couldn’t find an issue regarding this.
0