I'm dumping here some feedback from @kwridan

👋 not sure where the best venue is for feedback on the dependency injection framework for tuist is

From a cursory glance:

• the API doesn’t need to be async for thread safety (can use locks instead of actor internally) as with async in the API it bubbles to consumers of the DI which in turn would unnecessarily need to become async themselves
• The API should allow explicitly declaring the required type - this allows registering types for a protocol

registry.register(FooProtocol.self) { r in
FooImplementation()
}

• For purposes of testing something to consider is - would overrides of registrations be permitted, for example in an acceptance test, possibly have a real Assembly + a few select mock overrides? A few ways we can achieve this if needed

This is closer to what we demoed during Swift Heores

https://github.com/bloomberg/tuist/blob/poc/tuist-generator-assemblies/Sources/TuistGenerator/Assembly/TuistGeneratorAssembly.swift

You can browse the stub interfaces 😅