Yeah. If you&#x27;re concerned about limiting the amount of additional code one needs to understand in order to use part of a library of code, then the fix is relatively simple: make each function in your library depend on as little of the rest of the library as is possible.<p>If the author is <i>legitimately</i> concerned about code bloat from the unused parts of a library, Go&#x27;s linker needs to get a <i>lot</i> smarter.