Kai(luo) Wang

There is renewed interest [here](https://github.com/typelevel/cats/issues/1831) and [here](https://github.com/typelevel/cats/issues/1831#issuecomment-337323639) in moving alleycats into cats. That's probably the quickest way to move forward with Alleycats. I am going to submit a PR there.

alleycats moved into cats. Closing this. I'll submit a PR for readme update.

Sorry I am still on paternity leave. What I would like to test is if having delicate import trigger an unused import warning.

When concrete methods are being moved between abstract sealed classes whose usage is in a single inheritance hierarchy, the change should be deemed binary compatible. E.g. ```Scala sealed abstract class...

Being able to know explicitly what are being serialized is definitely useful. At kittens we also provide "semi auto" derivation alone side the full auto one. The full auto one...

The doge workaround specified in @eed3si9n wouldn't work if some modules have a custom `releasePublishArtifactsAction` right? Unless there is a way to set `releasePublishArtifactsAction` to a cross command like `+assembly`?

Just noticed another discrepancy in section 4.4.1: ``` cookie-octet = %x21 / %x23-2B / %x2D-3A / %x3C-5B / %x5D-7E / %x80-FF ; octets excluding CTLs, ; whitespace DQUOTE, comma, semicolon,...

You shouldn't need to add the resolver. This should be available in the default resolves. Try make sure you are on the latest sbt?

I apologize. I thought I left a comment but obviously, I didn't actually click the comment button. This feature will be pretty useful for sure. But I have concerns over...

should be an easy change right? If you are interested, a PR will be more than welcome. :)