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

doc: document typical runtime requirements of Go programs #3897

Open
gopherbot opened this issue Aug 2, 2012 · 12 comments

Comments

@gopherbot
Copy link

commented Aug 2, 2012

by hadrien.grasland:

While browsing the golang.org website, I was unable to find a satisfactory documentation
of the run-time requirements of Go programs.

I did explore the "tiny" toy OS kernel example of the Go source tree, but it
is now deprecated. The "How is the run-time support implemented?" FAQ entry,
on its side, only provides compiler-specific data, and with no guarantee that it will
remain valid in the future.

I believe that documenting these in the spec (the "System considerations"
section comes to mind) is important if Go is to be used for system programming tasks. As
of now, there is no way to clearly draw the line between what can be implemented in Go
and what must be implemented in a lower-level language like C or C++, in a manner that
won't change in the future. There is also no way to guarantee that switching or
upgrading compilers won't break existing Go system software by suddenly adding more
run-time requirements.
@robpike

This comment has been minimized.

Copy link
Contributor

commented Aug 2, 2012

Comment 1:

Labels changed: added priority-later, documentation, removed priority-triage.

Owner changed to @adg.

Status changed to Accepted.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Sep 12, 2012

Comment 3:

Labels changed: added go1.1maybe.

@davecheney

This comment has been minimized.

Copy link
Contributor

commented Jan 25, 2013

Comment 4:

Owner changed to @davecheney.

Status changed to Started.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Mar 12, 2013

Comment 5:

[The time for maybe has passed.]

Labels changed: removed go1.1maybe.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Jul 30, 2013

Comment 6:

Labels changed: added go1.2maybe.

@davecheney

This comment has been minimized.

Copy link
Contributor

commented Aug 5, 2013

Comment 7:

removing myself as the owner

Owner changed to ---.

Status changed to Accepted.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Nov 25, 2013

Comment 9:

Labels changed: added go1.3, removed go1.2maybe.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Dec 4, 2013

Comment 10:

Labels changed: added release-go1.3.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Dec 4, 2013

Comment 11:

Labels changed: removed go1.3.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Dec 4, 2013

Comment 12:

Labels changed: added repo-main.

@robpike

This comment has been minimized.

Copy link
Contributor

commented May 19, 2014

Comment 13:

Labels changed: added release-none, removed release-go1.3.

@rsc rsc added this to the Unplanned milestone Apr 10, 2015
@ysmolsky

This comment has been minimized.

Copy link
Member

commented Nov 12, 2018

We are not going to give promises about runtime in the spec for sure.
@aclements, can we close it down?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.