golang-google-wire

Compile-time dependency injection resolves the dependency graph during compilation using code generation, eliminating runtime containers and reflection. This makes errors apparent during compilation rather than at runtime, ensuring code reliability and maintainability.

You use google/wire by defining providers with wire.NewSet, building the dependency graph with wire.Build, and binding interfaces to concrete types with wire.Bind. The tool then generates plain Go constructor calls for your application.

No, google/wire does not require runtime reflection. It resolves dependencies at compile time by generating plain Go constructor calls, which eliminates the need for runtime containers and makes errors apparent during compilation.

You bind interfaces to concrete types in Golang using the wire.Bind feature. This ensures the dependency graph is unambiguous and allows you to explicitly map interfaces to their specific implementations within your provider sets.

Yes, you can organize providers into reusable sets using wire.NewSet. This allows you to group related providers together for easy composition and maintenance of your dependency injection graph across different parts of your application.

Compile-time dependency injection with google/wire requires an explicit code generation step before building, meaning dependency graph errors will block compilation. It is designed for explicit dependency resolution rather than dynamic runtime wiring.