-
Notifications
You must be signed in to change notification settings - Fork 176
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!: Template algorithms on track container frontend TrackContainer
#3193
refactor!: Template algorithms on track container frontend TrackContainer
#3193
Conversation
50f05ac
to
7bee8eb
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.
We can do this in principle, of course.
The main reason I didn't, was to lock down the template parameters a bit, as blanket "accept everything" parameters can be a bit confusing sometimes.
I suppose this can be alleviated by using a concept? There are already track container backend and multitrajectory backend concepts, so it should be fairly simple to assemble a combined track container concept. We could then use that to constrain the template types in these cases.
My primary reason was to break the template param dependency chain a bit. For example the fitters / finder / ambi res should not have to carry through the holder type and the mutability flag. Concepts would be great here I think! In principle the user should be able to create their own high level track container and proxy objects. Not sure if this is useful but I think the decoupling would be nice. I think this one is actually not critical at all for v36 btw. I am happy to push this a bit further if we cannot make it until we want to cut the major release. |
0c47ad0
to
3c050df
Compare
TrackContainer
TrackContainer
…plate-on-track-container-fontend
…plate-on-track-container-fontend
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.
Let's go
|
Instead of pulling all the track container template parameters into the algorithms we can template on the
TrackContainer
and get the details from there.blocked by