You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we have a case where we do actually use a default initialized particle for diagnostics.
I believe it's in order to forward the type to highfive to create a dataset, and the values are not "used" per se
other than that there some default initialized particles in tests
the simplest approach might be multiple classes, where the current "Particle" class becomes non-default construcbile, but it inherits from a super class "AParticle(?)" which is default constructible
or the particle class has an optional template param deciding if it's default constructible
Should we allow for default particle init? I don't think so unless it's so much trouble not to.
The text was updated successfully, but these errors were encountered: