Piotr Krzemiński

From this example it looks like the 0.4.2 behaviour was accidental and based on the fact that the `var`s in this example were public. Only that way you could even...

This case is not yet supported. Chimney would have to generate following code in order to support target compound types: ```scala val src = A(true) new A(src.a) with B {...

The problem with function provided by the user is that either (1) we sacrifice compile-time type safety and run the function in runtime allowing for runtime exceptions, or (2) we...

Seems like a reasonable feature under a flag (`enableParentAccessors`?). PRs welcome.

Hmm, I don't have strong opinion. For compatibility reasons we should probably keep it as it was before (don't perform lookup to a parent class). Do you see some other...

My concern about integration with `Sync` is that it doesn't belong to `cats-core`, but to `cats-effect` which means either depending on it in `chimney-cats` (bad) or introducing another integration module...

Hi, thanks for taking care of progressing that feature 👍 The only issue I see is that when you define two independent flags for naming conversion, one may enable them...

[This idea](https://github.com/scalalandio/chimney/pull/162#issuecomment-612909384) didn't allow to enable both conversion, but rather pick source and target encoding. It left some space for representing invalid conversions (like: from A to A), but it...

Sounds good 👍

The example from tests can be used: https://github.com/scalalandio/chimney/blob/master/chimney/src/test/scala/io/scalaland/chimney/examples/Shapes.scala