-
Notifications
You must be signed in to change notification settings - Fork 168
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
refactor!: use c++20 concept to define insert function for different types of seed collections #3367
Conversation
@paulgessinger @andiwand @CouthuresJeremy I have provided support also for the non C++20 code without changes to the API (if you do not count the change of The seed finder and filter now accept a global reference to the seed container (for the current code that is a Also, the signatures of the I'll add some tests to check and verify this. But this is good to be reviewed already, I think. /cc @pbutti who may be interested in seeding developments |
📊: Physics performance monitoring for 517989cphysmon summary
|
c423790
to
c1cc293
Compare
40bae82
to
249d8b7
Compare
28e8c8c
to
e7b0b67
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.
Thanks! Let's get this in.
Quality Gate passedIssues Measures |
Taking from @CouthuresJeremy 's PR I'm here proposing a possible alternative that would not even be a breaking change (unless I'm missing something). This will use c++20 concepts to define different versions of an
insert
function that will add a seed to the output collection.This will work with 'back_insert_operator' (as we currently do) as well as collection that support
push_back
and/orinsert
blocked by
edit: Now this is breaking since we do not support back_insert_operator option anymore