go plugin: don't put debugging symbols in generated binaries
Metadata
Current evaluation
Rejected. Maintainers prefer stripping Go binaries in the prime step, not at build time. The author confirmed post-build stripping yields identical results, making the change redundant.
Suggested action: —
No scores available.
Issue body
Go binaries should never stripped or they can behave badly,
but it's possible to avoid debugging symbol generation at build time.
The binaries are roughly half the size
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Rejected. Maintainers prefer stripping Go binaries in the prime step, not at build time. The author confirmed post-build stripping yields identical results, making the change redundant. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected as it conflicts with the strategy to strip binaries during the prime stage rather than at build time. Maintainers confirmed standard strip commands work on Go binaries, rendering the change unnecessary. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected and closed. Reviewers confirmed standard strip commands work on Go binaries and aligned with the project's plan to strip during the prime stage. The proposed build-time flag change conflicted with this workflow and was deemed unnecessary. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1858785 go plugin doesn't strip binaries | snapcraft (launchpad) | open | Feature request to add an option to strip binaries built by the go plugin to reduce snap size. 6.6 years old with zero comments and no labels; the go plugin has since been removed from snapcraft, making the request moot. |