I would make parenthesis with functions a must, to remove the ambiguity and the warnings of the kind variable "something" does not exist and is being expanded to "something()".

If you haven’t seen the recent updates to Dialyxir via transformations of the error messages by my Erlex library, I encourage you to seek them out. We now control all error messages, so any PRs to address deficiencies in language should be straightforward to add and not require any Erlang knowledge. If you have an editor’s hand, please consider doing so =)

If it fails to transform the message, it falls back to the Erlang output, so there’s no reason to not use it, if you’re already using Dialyzer.

Additionally, there’s a --explain flag that allows you to see what a particular error class would mean. We do not get enough information from Dialyzer currently to be able to give you an explanation of the specific error, but we can tell you what no_return means and give an example of what would cause that type of error. Warnings are listable by calling Dialyxir.Warnings.warnings/0.

keyed maps support in syntax / guards

OLD:
def verify(%{user_id: user_id, user_balance: user_balance}), do: user_id

NEW:
def verify(%{user_id, user_balance}) when user_balance > 0, do: user_id

Basically writing a map like %{user_id} implies to the compiler to expand it to %{user_id: user_id}

user_id = 5
new_map = %{user_id}

insert support too