c++ - Does std::span<T> remain valid and point to the new std::vector<T> upon move of a std::vector&

admin管理员组

文章数量:1387420

If we have an initialized std::vector

std::vector<T> v = ...;

then construct a span into that vector

std::span<T> s = std::span<T>(v.begin(), 10);

and then move the original vector

std::vector<T> x = std::move(v);

Is span s still valid? That it works in most implementations I have no doubt. Move is implemented as simple pointer swap and no reallocation occurs. It is then expected that the span still points to the original memory which is now managed by x. But this doesn't mean it is sanctioned to always work. Is this undefined behaviour that could be at risk of failure?

If we have an initialized std::vector

std::vector<T> v = ...;

then construct a span into that vector

std::span<T> s = std::span<T>(v.begin(), 10);

and then move the original vector

std::vector<T> x = std::move(v);

Is span s still valid? That it works in most implementations I have no doubt. Move is implemented as simple pointer swap and no reallocation occurs. It is then expected that the span still points to the original memory which is now managed by x. But this doesn't mean it is sanctioned to always work. Is this undefined behaviour that could be at risk of failure?

• c++
• c++20
• stdvector
• stdmove
• std-span

Share Improve this question Follow edited Mar 18 at 9:27 JeJo 33.5k77 gold badges5555 silver badges9595 bronze badges asked Mar 17 at 9:01 bradgonesurfingbradgonesurfing 32.3k2020 gold badges124124 silver badges233233 bronze badges 2

• If it is std::vector<T, A> it can surely become invalid, and I don't see a strong reason for the standard to explicitly make std::allocator a special case for this scenario either. So I would assume that it is unsafe. – Weijun Zhou Commented Mar 17 at 9:19
• 2 I just found on cpp reference After container move construction (overload (8)), references, pointers, and iterators (other than the end iterator) to other remain valid, but refer to elements that are now in *this. The current standard makes this guarantee via the blanket statement in [container.reqmts]/67, and a more direct guarantee is under consideration via LWG issue 2321. which should cover it as being blessed!`` en.cppreference/w/cpp/container/vector/vector – bradgonesurfing Commented Mar 17 at 9:22

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 4

See

https://en.cppreference/w/cpp/container/vector/vector

After container move construction (overload (8)), references, pointers, and iterators (other than the end iterator) to other remain valid, but refer to elements that are now in *this. The current standard makes this guarantee via the blanket statement in [container.reqmts]/67, and a more direct guarantee is under consideration via LWG issue 2321.

本文标签：