Right now one can override a mix task in mix.exs. It would be useful if one
could still access the 'original'.
My use case:
Our 'mix test' is remapped to reset the DB, etc which is what we need for
the CI, etc.
However, I want to be able to run an individual test in order to drive the
code a
Right now one can override a mix task in mix.exs. It would be useful if one
could still access the 'original'.
My use case:
Our 'mix test' is remapped to reset the DB, etc which is what we need for
the CI, etc.
However, I want to be able to run an individual test in order to drive the
code a
anything else
> end
> Mix.Tasks.Test.run(args)
> end
> ```
>
> You could expand the logic of the function further to look for CI specific
> env variables etc
>
> On Thu, 30 Sep 2021, at 7:24 AM, Generic Jam wrote:
>
>
> Right now one can override a m
Somehow you'd have to understand if the tail recursion in that situation is
beneficial or not.
https://www.erlang.org/doc/efficiency_guide/myths.html#myth--tail-recursive-functions-are-much-faster-than-recursive-functions
Best,
Kevin
On Wed, 15 Jun 2022 at 16:18, Adam Lancaster wrote:
> Do
I recently wrote an internal lib that for many functions it takes a list or
a stream and returns a stream. It's the responsibility of the user to run
the stream. For my use case I used a guard which only permitted a list or a
struct (Stream) as I couldn't figure out a better system. For my tests
