Get the latest tech news
Is C++26 getting destructive move semantics?
Can I express a function that consumes an object? Meaning that its destructor is not run on the moved-from object? Like the proposed library function trivially_locate_at itself? template <class ...
None
Or read this on Hacker News