Skip to content
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

Enforce filling gaps #4921

Open
chillenzer opened this issue May 31, 2024 · 0 comments
Open

Enforce filling gaps #4921

chillenzer opened this issue May 31, 2024 · 0 comments
Assignees
Labels
component: core in PIConGPU (core application) refactoring code change to improve performance or to unify a concept but does not change public API

Comments

@chillenzer
Copy link
Contributor

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.

PrometheusPi added a commit that referenced this issue Jun 10, 2024
Changes to Synchrotron Radiation from issue #4921. Part 1.
@steindev steindev added refactoring code change to improve performance or to unify a concept but does not change public API component: core in PIConGPU (core application) labels Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: core in PIConGPU (core application) refactoring code change to improve performance or to unify a concept but does not change public API
Projects
None yet
Development

No branches or pull requests

2 participants