These were already used inconsistently, i.e:
so just nuke all the redundant ;. Some also just dropped in https://github.com/bitcoin-core/libmultiprocess/commit/bd508311b5617bd8d31b875d8781392f2a6ad7be.
These were already used inconsistently, i.e:
so just nuke all the redundant ;. Some also just dropped in https://github.com/bitcoin-core/libmultiprocess/commit/bd508311b5617bd8d31b875d8781392f2a6ad7be.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline and AI policy for information on the review process. A summary of reviews will appear here.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
mp::ConnectStream) by xyzconstant)If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
574 | done.set_value(); 575 | })); 576 | }); 577 | done.get_future().get(); 578 | - KJ_EXPECT(error_thrown); 579 | + KJ_EXPECT(error_thrown)
hmm, for macros, I generally prefer if they enforce a trailing semicolon.
Though, it may be too late to fix this now?
Then perhaps omit -Wextra-semi-stmt?
Seems fine, but I am -0
Yea. I don't have too much of an opinion, but it wasn't clear to me why a PR labelled "CI" (#321) was also making random source code changes (bd508311b5617bd8d31b875d8781392f2a6ad7be) (although it seems like that PR was generally confusing (https://github.com/bitcoin-core/libmultiprocess/pull/321#issuecomment-5171132506)), so thought we could at least make this consistent.
I think 321 was dropping it after a function def, this one is dropping it after statements.
... random source code changes (bd50831)...
See #321 (review).
See #321 (review).
Thanks. It would be good to write commit messages that contain information for other contributors (which then persists over time), so they don't have to search through GitHub comments to try and find context/explanations.