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

exit-once: Clarify that run() ins't prescriptive #190

Merged
merged 2 commits into from
Jul 26, 2023

Conversation

abhinav
Copy link
Collaborator

@abhinav abhinav commented Jul 26, 2023

Clarify that the example of using run() and log.Fatal isn't intended
to be prescriptive.

Provide samples of using os.Exit directly, using different exit codes,
and clarify that there's flexibility here on how everything is set up.

Refs #189

abhinav and others added 2 commits July 26, 2023 04:46
Clarify that the example of using `run()` and `log.Fatal` isn't intended
to be prescriptive.

Provide samples of using `os.Exit` directly, using different exit codes,
and clarify that there's flexibility here on how everything is set up.

Refs uber-go#189
Copy link
Member

@mway mway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, LGTM. Thanks @abhinav!

@mway mway merged commit 7f06a53 into uber-go:master Jul 26, 2023
@abhinav abhinav deleted the exit-once-clarify branch July 26, 2023 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants