The warning itself is not a bug because the compiler is being smart and saying: “this will always fail”. That happens because you are passing a literal and the compiler can figure it all out. If you move the tuple to a variable instead of passing it directly to the guard, then the compiler should stay quiet.
I would say the warning in the last example is wrong though, it won’t “fail with ArgumentError”, but it will “always return false”. Although the wrong messaging is a bug in Erlang, not in Elixir.
@josevalim Is there planned support for a max column width option in the formatter? Most of my codebases wrap at 80 chars, but the formatter will unwrap anything between 80 and 100 chars. I can restructure most things to keep the limit, but seem to be out of luck for long aliases and functions with guard clauses.
Formatting is done with the Code.format_string!/2 function. A .formatter.exs file can also be defined for customizing input files and the formatter itself.
So anyone reading docs should at least check it, but I don’t found that parsed arguments are passed directly to it!
To be honest there is a section for arguments where no length is described and next section called .formatter.exs describes extra arguments. Keeping in mind that there is no info that arguments are passed to linked function it could be wrong interpreted like:
There are no more options other than described, however .formatter.exs supports few more. Unfortunately there are also no such option supported there.`
Reading this first time I through similarly. I was need to read source of this task to be sure.
btw. @josevalim
I found that this link for docs in v1.7.0-dev points towards v1.5.3 version which is big mistake, because this version does not have implemented linked function!
The link that doesn’t work is a lesser problem than options for mix format not being listed on the one page you would expect them, but yes, the link working exacerbates that considerably.
Author of this probably wanted to say that these options are task-specific only. There is no need to describe same options in multiple places. The real problem is text (and it’s location) that links to rest of options - it could be missed.
I think that sentence with this link should be a little changed and moved to Options section, so it will be easier to find it.
