Reflection warnings with *warn-on-reflection* enabled

[serioga]

If I enable *warn-on-reflection* globally then there are warnings in cats code.

Reflection warning, cats/context.cljc:38:19 - call to java.lang.IllegalArgumentException ctor can't be resolved.
Reflection warning, cats/util.cljc:34:14 - call to method write on java.io.Writer can't be resolved (argument types: unknown).
Reflection warning, cats/monad/maybe.cljc:65:17 - reference to field v on java.lang.Object can't be resolved.
Reflection warning, cats/monad/either.cljc:70:17 - reference to field v on java.lang.Object can't be resolved.
Reflection warning, cats/monad/either.cljc:100:17 - reference to field v on java.lang.Object can't be resolved.
Reflection warning, cats/monad/either.cljc:183:12 - reference to field v on java.lang.Object can't be resolved.
Reflection warning, cats/monad/either.cljc:159:19 - reference to field v on java.lang.Object can't be resolved.
Reflection warning, cats/monad/either.cljc:165:19 - reference to field v on java.lang.Object can't be resolved.
Reflection warning, cats/monad/either.cljc:166:19 - reference to field v on java.lang.Object can't be resolved.
Reflection warning, cats/monad/either.cljc:174:20 - reference to field v on java.lang.Object can't be resolved.

[ghost]

Thanks for reporting, we can try to get rid of those, maybe even enable *warn-on-reflection* on tests for detecting these things.

[sfnelson]

This issue can probably be closed, unless you want to keep it open to track the remaining reflection warnings in the cats.labs.* namespaces

[ghost]

If there are still a few warnings under cats.labs.* let's leave this open. We'd like to avoid reflection ieverywhere f it's possible.