Memory Resource Retrieval, main branch (2026.01.08.)#347
Merged
krasznaa merged 4 commits intoacts-project:mainfrom Feb 18, 2026
Merged
Memory Resource Retrieval, main branch (2026.01.08.)#347krasznaa merged 4 commits intoacts-project:mainfrom
krasznaa merged 4 commits intoacts-project:mainfrom
Conversation
|
6b80cc1 to
571f8af
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Triggered by acts-project/traccc#1226, I spent some time in making it possible to get the memory resource used by various memory holder types. Even if
vecmem::edm::hostalready had this functionality, which I only realised after starting to work on this whole thing. 😛It is really only for
vecmem::data::jagged_vector_bufferthat getting its memory resource(s) gets complicated. But hopefully I managed to land on a correct logic in the end. 🤔