Reflection lets code discover and call program elements at runtime instead of using direct references. Because the compiler cannot determine which parts are needed, reflection can force unused code to remain in the build. section 8.2.2
Treat reflection as a dependency-size risk during build analysis. Inspect large packages and trace their shortest dependency paths before replacing or removing libraries; in Go, use binary analysis to identify reflection-heavy packages. section 8.2.2
Go binary investigation
After stripping symbols and debugging information from a production Go binary, use a size analyzer to locate remaining large packages. Investigate reflection-heavy libraries because their runtime discovery can prevent the compiler from removing unused code. section 8.2.2













