Mateusz Borek

Hi, sure: * `support for recursive types` I should actually call it recursive class. I see that, there are already defined tests for them (e.g. `GPerson`/`RPerson` and `Recursive`) but it...

> I think we wanted to try a two-level solution, where the .derived method is available via an extension which requires the implicit configuration; the extension then implements the Derivation...

We haven't released macwire support for Akka in Scala 3 yet

Thanks for reporting the issue! It's pretty interesting, because when we change `PrometheusMetrics.default` application to ```Scala autowire[Dependencies]( config.api, config.user, config.passwordReset, config.email, DefaultIdGenerator, clock, sttpBackend, PrometheusMetrics.default[IO]( namespace = "tapir", registry =...

Right, I thought that we may use autowire to create instances of `PrometheusMetrics` unintentionally, but it seems it's not the case. No, unfortunately, I don't have any small test case...

I've managed to create a test case for this issue ``` case class A() case class B(i: Int, s: String) object B { //the order matters in this case -...

The next step may be to verify if it is possible to add support for other return types like `ZManaged` or an effect that meets some requirements

ok, makes sense. It would be also good to create a pure autowire implementation. https://github.com/softwaremill/macwire/issues/191

Adding compile-time configuration might be also useful to define a default trait implementation that should be wired. To do so, we may introduce a tag `useClass[A]` or `useImplementation[A]` that would...

Looks promising for me, but I would rather name the function that @adamw proposed `wireResourceRec` to keep it "compatible" with `wire`/ `wireRec`. When it comes to the `Resource` I think...