Enforce filling gaps #4921
Labels
component: core
in PIConGPU (core application)
refactoring
code change to improve performance or to unify a concept but does not change public API
In #4916 (comment) I've stumbled across a commented warning to always fill the gaps after an operation. If necessary, we should have a mechanism to enforce this. Theoretically, this could be done via compile-time list operations and tagging of the corresponding manipulators. Practically, we will probably wait until we have the init pipeline at runtime which will make this kind of operation easier to implement.
The text was updated successfully, but these errors were encountered: