Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go: name temporary binary after first file in 'go run' #3503

Closed
rsc opened this issue Apr 9, 2012 · 5 comments
Closed

cmd/go: name temporary binary after first file in 'go run' #3503

rsc opened this issue Apr 9, 2012 · 5 comments
Milestone

Comments

@rsc
Copy link
Contributor

rsc commented Apr 9, 2012

cmd/go: name temporary binary after first file in 'go run'
No one likes 'a.out' anymore.  It appears in ps and top while
the program is running.
@rsc
Copy link
Contributor Author

rsc commented Apr 9, 2012

Comment 1:

Note that this is not completely trivial.  Using a.out means that we avoid conflicts
with the import path-named archives that coexist in that temporary directory, unless
they begin with "a.out/" in violation of the 'use a name you own' rule.
Switching to the basename of the first Go file probably means we have to make a separate
directory to hold that object.

@rsc
Copy link
Contributor Author

rsc commented Dec 10, 2012

Comment 2:

Labels changed: added size-m.

@rsc
Copy link
Contributor Author

rsc commented Jan 31, 2013

Comment 3:

This issue was closed by revision 8b6534b.

Status changed to Fixed.

@davecheney
Copy link
Contributor

Comment 4:

This is nice. When running go run ../test/run.go, top will show the names of the
bugs/issues as it progresses.

@rsc
Copy link
Contributor Author

rsc commented Feb 5, 2013

Comment 5:

nice.

@rsc rsc added fixed labels Feb 5, 2013
@rsc rsc self-assigned this Feb 5, 2013
@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc removed their assignment Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants