*Problem*
Functions that convert or work with time units, i.e.
`System.convert_time_unit/1`, `DateTime.add/3` and `Time.add/3` are limited
to working with a subset of possible time units. The current subset of *named
units* includes `:second`, `:millisecond`, `:microsecond`, and
I’m in favor of the addition overall. The specific function name matters less
to me, /1 or /1 would be fine.
> On Jul 2, 2019, at 16:02, Bruce Tate wrote:
>
> I could learn to like /1, and also think that /1 fits Elixir's style
> of abbreviation. My vote is for either one of those.
>
> -bt
If anything this seems more suited to be a warning rather than something
deprecated and slated for removal. It would be similar to how the compiler
suggests pattern matching on an empty list instead of length(list). The
difference being that there are performance differences for pattern
www.plataformatec.com.br[1]
> Skype: jv.ptec
> Founder and Director of R
>
>
>
> On Thu, Jul 13, 2017 at 4:45 PM, Parker Selbert <parker.selb...@gmail.com>
> wrote:>> Recently I discovered an application bug that stemmed from the use
> of MapSet.subset?/2. Th
Recently I discovered an application bug that stemmed from the use of
MapSet.subset?/2. The code was attempting to check whether there was any
overlap between two sets, but the use of subset?/2 is order dependent. The
solution was to use MapSet.disjoint?/2 and check if the result was false,
I'm strongly in favor of the proposal, it is an ideal use of protocols
(and we aren't facing a non-BIF penalty).
— Parker
On Fri, Jun 16, 2017, at 03:51 PM, OvermindDL1 wrote:
> Sounds like precisely what is needed. I'm all for it!
>
>
> On Friday, June 16, 2017 at 2:16:59 PM UTC-6,
Ever since getting involved in Elixir I have been relieved that there
isn't any debate between ' and ", or remembering which supports
interpolation. Learning the distinction between binaries and charlists
is important when it comes to interfacing with Erlang modules, but that
is something you do
