the implicits for TupleConverter and TupleSetter can lead to subtle bugs at
times. i think its because of the low priority defaults for any generic
type.
for example i ran into issue where an implicit wasn't propagated by
mistake, and it seemed to fall back on an incorrect generic choice without
a
How can we fix this? Without having a single value be the default, lots of
code won't actually work. I agree it is not the safest thing, but I don't
think it can easily hit you in the TypedPipe API which is what we have
recommended for years now.
On Sun, Sep 18, 2016 at 09:32 Koert Kuipers wrote:
yeah agreed, it just caught me by surprise somewhat
On Sun, Sep 18, 2016 at 5:48 PM, P. Oscar Boykin
wrote:
> How can we fix this? Without having a single value be the default, lots of
> code won't actually work. I agree it is not the safest thing, but I don't
> think it can easily hit you in th
