cmd/go: stop writing pkg.test executable in directory when profiling? #46086
Labels
GoCommand
cmd/go
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
Milestone
results in cmd/go writing
pkg.test
to the current directory. The original reason was so thatpkg.test
would be handy when runninggo tool pprof
. Butgo tool pprof
no longer requires access to the original executable, because the requisite information is in the profile itself.Maybe we should stop writing it.
The text was updated successfully, but these errors were encountered: