Lightning Talk: Writing a Better std::move - Jonathan Müller - CppCon 2023

cppcon.org/
---
Lightning Talk: Writing a Better std::move - Jonathan Müller - CppCon 2023
github.com/CppCon/CppCon2023
std::move allows the creation of const rvalue references, which is almost always wrong. It also allows moving out of lvalue references, which can be dangerous since you don't have real ownership over them and a caller might not expect the object to disappear. Let's fix those problems using macros, reflection, and more macros.
---
Jonathan Müller
Jonathan is a library developer at think-cell. In his spare time, he works on various C++ open source libraries for memory allocation, cache-friendly containers, or parsing. He also blogs at foonathan.net and is a member of the C++ standardization committee.
---
Videos Filmed & Edited by Bash Films: www.BashFilms.com
KZbin Channel Managed by Digital Medium Ltd: events.digital-medium.co.uk
---
Registration for CppCon: cppcon.org/registration/
#cppcon #cppprogramming #cpp

[@skulver]

I'm not sure if I'm more impressed by the level of knowledge on display or if I'm more horrified by the level of knowledge required to write a move function. Definitely a video that warrants a few watches because there's a lot in there. Well done!

[@foonathan]

Thanks!

[@employeeofthemonth1]

Excellent talk this!

[@foonathan]

Thanks!

[@zbychs]

Very interesting, thanks.

[@passerby4507]

Intriguing, but not entirely convinced it's a good idea.

[@jopa19991]

really decent talk

[@314Labs]

The ending 😆.

[@RN-rm7gd]

Hmm, i fear it's a dump question. But why do you move in the first place? Or is make_padding designed not to take a reference? Anyways, designing a function in a way of moving around a pointer which than is expected to end up in the original parameter doens't feel right in the first place. Ronald.

[@foonathan]

It's just a silly example, but the idea was that you want to create a tree of widgets, where the "padding widget" owns the "content widget", hence the move.

[@aniketbisht2823]

How are compile times affected? Especially given the usage of "is_id_expression".

[@foonathan]

They didn't get noticeable worse. You can also disable the is_id_expression check in most builds for example, as it doesn't affect code generation and is just an extra lint against misuse.

[@KX36]

don't watch an hour lecture on move semantics, watch this instead!