-
Notifications
You must be signed in to change notification settings - Fork 1.2k
refactor: implement irange::range and use it #4788
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
Conversation
| @@ -0,0 +1,90 @@ | |||
| // Copyright (c) 2021 The Dash Core developers | |||
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.
along with referring original implementation as a source, adding their copyright is probably for the best, also mention the commit of cpp_range from which this was derived from
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.
They didn't have a copyright on the file, just a MIT license in the folder
|
see latest |
|
This pull request has conflicts, please rebase. |
ca2fb53 to
1645242
Compare
| workerPool.push([pQuorum, t, this](int threadId) { | ||
| for (size_t i = 0; i < pQuorum->members.size() && !quorumThreadInterrupt; i++) { | ||
| for (const auto i : irange::range(pQuorum->members.size())) { | ||
| if (!quorumThreadInterrupt) { |
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.
| if (!quorumThreadInterrupt) { | |
| if (quorumThreadInterrupt) { |
|
pls see 49f76c6 |
|
This pull request has conflicts, please rebase. |
88c31b0 to
c5572b0
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.
utACK
68a4ac2 to
50f31b2
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.
utACK
#5732) ## Issue being fixed or feature implemented #4788 (comment) noticed while working on #5731 ## What was done? ## How Has This Been Tested? run a node, check logs - there is a meaningful time span between `start` and `done` now and not just zeros all the time. ## Breaking Changes ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
No description provided.