-
Notifications
You must be signed in to change notification settings - Fork 226
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
Tidy up bootstrapping #225
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Initial feedback written from mobile.
0d9a438
to
9055bd6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replied to comments; sorry for blocking, but some items need addressing.
The PR now also includes the removal of BootstrapOnSignal with a replacement, and its demonstration in the tests. |
We do not break things without good reason. We have many users simply using go get and we try very hard to not put unnecessary burden on our users by changing things at whim. |
|
WRT this patch, I actually agree with adding the context argument to those functions. I just want to avoid using "downstream users can deal" as an excuse. |
Was this pull request ever approved before merging? |
No. |
Refactor bootstrapping to remove goprocess, and use contexts properly. Also includes some interface assertions for future refactoring.