C++ - Implementation Challenge: Replacing std::move and std::forward 44 points · submitted Sep 2020 by u/alecco 44 comments · 87% upvoted · source · other discussions
move()andforward()are terse enough. Implement them as language features? Possibly. But it might encourage their over-use. I suspect that's why they're implemented as they are.I don't see the macros as worth it.
Plorkyeran 10 points · Sep 2020
The advantage of the macros is compile time and better debugger behavior, not terseness.
pork_spare_ribs 4 points · Sep 2020
Better debugging behaviour in unoptimised builds sounds reasonable. 250ms fixed cost of compile time is pushing the boundaries of reasonable.
atilaneves 1 points · Sep 2020
I get annoyed when compiling a file takes 250ms in total.