We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
PdiEvent::and_with
We have both PdiEvent::with and PdiEvent::and_with. I am not convined of the benefit in practice as it is still readable to chain with calls
PdiEvent::with
with
PdiEvent("event") .with("data1", data1) .with("data2", data2);
I strongly suggest we keep a single version.
The text was updated successfully, but these errors were encountered:
@EmilyBourne any opinion on this ?
Sorry, something went wrong.
I would tend to agree with you. I don't see a reason to have 2 methods that do the same thing.
In Gyselalib++ we are using: https://github.com/gyselax/gyselalibxx/blob/86d95abd5672362c600714d6cb4c5abbd0dc9c7c/src/geometryXYVxVy/time_integration/predcorr.cpp#L58-L62
but probably we are just copying across whatever was done the first time.
Successfully merging a pull request may close this issue.
We have both
PdiEvent::with
andPdiEvent::and_with
. I am not convined of the benefit in practice as it is still readable to chainwith
callsI strongly suggest we keep a single version.
The text was updated successfully, but these errors were encountered: