Hi there!
Thank you for an awesome library.
We faced a problem with the namespacing:
The library name is Factory, there is also a struct called Factory<T> in the library.
We have a custom structure that is also named Container.
We have tried to distinguish the Factory's Container by adding Factory.Container.shared.myService1() but it doesn't work since there is an struct Factory<T> that already took the Factory name.
In summary, we can not use the name Container for new structure anymore, since it conflicts with Factory's Container and we can not use Factory.Container when there is already a struct Factory<T> in the library. (The compiler is confused between struct Factory<T> and module name Factory>.
Hi there! Thank you for an awesome library. We faced a problem with the namespacing:
Factory
, there is also a struct calledFactory<T>
in the library.Container
.Factory.Container.shared.myService1()
but it doesn't work since there is anstruct Factory<T>
that already took the Factory name.In summary, we can not use the name
Container
for new structure anymore, since it conflicts with Factory's Container and we can not useFactory.Container
when there is already astruct Factory<T>
in the library. (The compiler is confused betweenstruct Factory<T>
and module nameFactory
>.I suggest renaming the
Container
toDIContainer