Diego Alonso

@bplommer The build seems to be working fine as of now. It was rebased to `series/0.23`.

> I'm on the fence about this change. By making WithContext[Msg, A] take parameters for both of its members, we've basically made it a Tuple2. This is more general, but...

> I think a backend solution would be preferrable for 0.21. Since the body is a black box until compiled, perhaps we could add a process that, at the point...

@bplommer What would be the state for this Pull Request? You have proposed some of the changes in this PR in separate Pull Requests: - #5712 Covariant Messages - Minimum...

We have found a similar problem in https://github.com/Banno/vault4s/ between versions `v.5.1.0` and `v.5.2.0`: - In that case we also have an inner `AnyVal` and the build for the latter would...

@raboof Just for my ease of mind... if someone writes a `fili` library, that depends on Vault4s 5.1.0, fetches that binary, compiles his binary jar to target `5.1.0`, publishes it;...

> The only major concern here would be around ScalaJS support. In other projects there is a separation of sources that are JS-specific or JVM-specific. Perhaps we can do the...

Taking existing support into account, I have opened PR to integrate this into the `cats.kernel`...

@joroKr21 From the last message, can we understand that you would like to withdraw this proposal? Is this something that should be reconsidered once we deprecate Scala 2.13?

@kailuowang In the title _tagless related util from freestyle_, which components of `freestyle` should be ported to `cats-tagless`? Porting the macros should not be difficult, since they are written on...