Jagged Vector Buffer Fix, main branch (2025.04.01.) #319
Conversation
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
krasznaa
added
bug
krasznaa
force-pushed
the
JaggedBufferFix-main-20250401
branch
from
bf3cd6b to
cc8f8bc
Compare
krasznaa
force-pushed
the
JaggedBufferFix-main-20250401
branch
from
cc8f8bc to
0faa4eb
Compare
krasznaa
force-pushed
the
JaggedBufferFix-main-20250401
branch
from
ea18956 to
37c646b
Compare
|
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.
@stephenswat found in acts-project/traccc#908 that currently it's not possible to create a
vecmem::data::jagged_vector_bufferobject withvecmem::vectorfor its size(s). This PR is meant to fix this.