>>=

FYI this is a typical workaround the typeclass author can implement https://gitlab.com/fommil/scalaz-deriving/blob/master/examples/xmlformat/src/main/scala/xmlformat/DerivedXDecoder.scala#L312-322

I don't see why this would be advantageous. Many projects are choosing to build on top of the Typelevel stack without getting under their "jurisdiction" for want of a better...

@diesalbla writing a separate intellij plugin is not difficult. I did it already for `@deriving` and it was quite easy. https://github.com/JetBrains/intellij-scala/pull/388 The code has changed a little bit since then...

I'm not sure codegen works for companions... a companion must be in the same file.

(unless the companion extends from some trait that you define in the codegen)

I'm +1 for LGPL. If we want to include code from scalaz7 we need to include their LICENSE (or, infeasibly, ask everybody to relicense, which is not worth it). That...

@jdegoes oh it is bsd3, i.e. the scalaz7 license, we can change that for 2.0.0 with the bifunctor to whatever you want.

Nobody is saying no to LGPL in this thread, but @tonymorris has said in chat that he opposes it and has heard feedback from other contributors who oppose it. We...

I agree, I don't think we're missing out on contributions at the moment because of the license. If I am prepared to use BSD3 then anybody else, except perhaps Stallman,...

@varming that's an interesting position your company is taking, I've not heard of any scala company accepting GPLv2 but not GPLv3! Note that GPLv2 is also incompatible with Apache 2.0,...