-
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
fix!: make material validity checks and construction explicit #3494
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.
I like
Core/include/Acts/Propagator/detail/PointwiseMaterialInteraction.hpp
Outdated
Show resolved
Hide resolved
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.
There's a lot of static_cast
ing going on now, do we need all of this? Does going to double
consistently give other issues?
I think for this PR, I could be fine to remove the |
@AJPfleger Ok |
What should be the next steps in this PR? |
I think the current version classifies as breaking. As such we would have to wait for the next major version bump to bring this in. Alternative to this is to keep the existing functionality and mark it as deprecated |
Quality Gate passedIssues Measures |
needs fixes in athena |
false alarm the failure seems to come from another PR |
By having the validity check explicit and forbid construction with type conversation, we avoid common pitfalls for the user[1].
The
AverageMaterials
had to be reworked a bit, since we were doing a lot of implicit type conversions in there. On different compilers we got different results. Now it should be stable.Thanks also to @paulgessinger for sending me in the correct direction.
[1] The user is me, trying to debug for hours why I get always vacuum material, which could have been caught earlier, by not allowing implicit conversions.