-
Notifications
You must be signed in to change notification settings - Fork 87
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
Dialyzer output #98
Comments
@josevalim any idea of what's going on here? |
Not sure. :( |
When I search phoenix repo for dgettext or dngettext this turns up: Is it because the first argument is an atom? |
@johnkelly the typespecs for those seem correct though: https://github.com/elixir-lang/gettext/blob/master/lib/gettext.ex#L501 I am thinking then it may rather be an issue with the macros defined in the Gettext backend? |
@josevalim is right, dialyzer is complaining about the macros defined by I really have no idea what's going on here 😕 |
@ericmj and @fishcakez, I'm gonna go ahead and ping you as well here cause I really don't know where to start. Any ideas? |
Sorry, I don't use dialyzer. |
I put this in my gettext.ex module to silence these warnings. @dialyzer [{:nowarn_function, 'MACRO-dgettext': 3},
{:nowarn_function, 'MACRO-dgettext': 4},
{:nowarn_function, 'MACRO-dngettext': 5},
{:nowarn_function, 'MACRO-dngettext': 6},
] |
@josevalim do you think it would be reasonable to put that in Gettext backends when we |
@whatyouhide I think we should rather fix this. @jeremyjh can you provide a simple app that reproduces those warnings so it makes it easier for us to fix this? Thank you! |
This is fixed on Elixir master and the v1.3 branch, so will be included in |
mix.lock
Relevant mix.exs dialyzer configuration in project function
On a brand new elixir 1.2.5 phoenix project, I get the following output from the dialyzer.
The text was updated successfully, but these errors were encountered: