News for hackers. Stuff that matters.

A comment on C++ std::move doesn't move anything: A deep dive into Value Categories. Parent comment

Re:C++ std::move doesn't move anything: A deep dive into Val... by dbcpp on Sunday January 11, 2026 @09:30AM (#46576056)
I would argue performance-noexcept-move-constructor should always be on. Move constructors should almost always be noexcept since they typically just move pointers around and don't do allocations normally.
[ Parent | on HN ]
Re:C++ std::move doesn't move anything: A deep dive into Val... by jcelerier on Sunday January 11, 2026 @11:50AM (#46577305)
eh, depends. for instance think about a small_vector or small_string
[ Parent | on HN ]
Re:C++ std::move doesn't move anything: A deep dive into Val... by dbcpp on Sunday January 11, 2026 @11:55AM (#46577353)
True, in that case it should just inherit the noexcept status of the object it holds.
[ Parent | on HN ]