Hi,
I think an invert() method on Map would be convenient to use. It is only a
handful of lines of code to add to a custom program, but why should users
need to do that? In my opinion this basic functionality should be
implemented by the Map module.
The invert() method would operate the
> At the same time, I am also an advocate for readability of code.
Really? Imho, code examples above with extra spaces are awful to read.
вторник, 5 февраля 2019 г., 13:01:47 UTC+3 пользователь Chris Hicks написал:
>
> I read and agree with the basic principle outlined there. I can definitely
I read and agree with the basic principle outlined there. I can definitely
see the issue with an ever growing list of options, especially those that
would allow for code to diverge quite a bit in the look between
applications. There does need to be consistency.
At the same time, I am also an
Hi Chris,
To quote one of the design principles behind the formatter [1]
> The second principle is to provide as little configuration as possible.
This eases the formatter adoption by removing contention points while
making sure a single style is followed consistently by the community as a
While it's not a style I have seen often in Elixir code, though I've seen
it elsewhere, I've found myself coding in a particular style that, for me
at least, increases the readability of my code and I'd love to see an
option in the formatter to allow for it.
Essentially it all boils down to
