[Common] Prevent dangling reference error when switching from gsl::span to std::span
#11699
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.
In the original code a temporary iterator to fv0a/fv0c is created and immediately discarded, leaving the result of
amplitude()(which is a span, a non-owning view) a with dangling references to the internals of the iterator. This worked by accident, since the underlying array in shared memory is available regardless, but can potentially lead to problems. Switching fromgsl::spanto thestd::span(PR AliceO2Group/AliceO2#14421) makes the original code fail to compile.@ddobrigk @ktf