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: clarify that main's return value may change #727

Merged
merged 1 commit into from
Jan 15, 2018
Merged

Conversation

ppannuto
Copy link
Member

Proposed changes:

[Doc-only]

In reviewing #714, I got to thinking about process behavior, in particular main's return code. Perhaps we should attribute it some significance (e.g. kill processes where main failed somehow, maybe respawn if error > 0, kill < 0). Not necessarily a debate to have today, just a thought to let rattle around. In the meantime, be explicit that main should return 0 for forward compatibility.

In reviewing #714, I got to thinking about process behavior, in particular `main`'s return code. Perhaps we should attribute it some significance (e.g. kill processes where `main` failed somehow, maybe respawn if error > 0, kill < 0). Not necessarily a debate to have today, just a thought to let rattle around. In the meantime, be explicit that main should return 0 for forward compatibility.
@alevy alevy merged commit 7299d6c into master Jan 15, 2018
@alevy alevy deleted the ppannuto-patch-1 branch January 15, 2018 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants