Maksim Volkau

Arguably, using factory method may be replaced by delegate registration. Though it is uncontrollable black box for container (increasing chance for runtime errors), it works. Interesting that I do not...

Hi Andrey, Agree on Convenience... may be I have time after I done with DryIoc V2. Thanks for project, it could be very helpful for someone to convince on using...

Lately I've got an interesting setup in scope of this [issue](https://bitbucket.org/dadhi/dryioc/issue/107/named-scopes-depending-on-resolved-types) in [DryIoc](https://bitbucket.org/dadhi/dryioc/). I suppose such setups are not particularly rare, and I am not sure how to handle them...

Hello, You are probably right about fragile design in this case. I've got the example as is. But what if you have a lot of legacy/existing code like that? Should...

Why not... ``` public enum QType { In, Out, Error } c.Register(made: Made.Of(() => new QueueProcessor(Arg.Of(QType.In), Arg.Of(QType.Out), Arg.Of(QType.Error)))); ```

Use #375 in .NET 8

Nope for the #375 until [UnsafeAccessorTypeAttribute](https://github.com/dotnet/runtime/issues/90081) is supported (likely in .NET 9)

Hope it will be fixed for you @sramananthula by #544

outdated

Тогда интересно увидеть обновленную версию. Если что-то прикручивать, то к актуальному. Под дебагер френдли имеешь в виду fluent синтакc, типа New blah? Буду разбираться с твоим транспайлером, очень интересно как...