Re:Catching use-after-move C++ bugs with Clang's consumed an...
by jeremyjh on Wednesday July 10, 2019 @02:20PM
(#20404750)
They were coming in C++17 too.
[ Parent
| on HN ]
Re:Catching use-after-move C++ bugs with Clang's consumed an...
by zone411 on Wednesday July 10, 2019 @02:32PM
(#20404885)
Back 2015, when the work on C++14 was still going on, it was already known that modules probably won't make into C++17. Very different situation now.
https://botondballo.wordpress.com/2015/06/05/trip-report-c-s...
Re:Catching use-after-move C++ bugs with Clang's consumed an...
by pjmlp on Wednesday July 10, 2019 @03:35PM
(#20405623)
The set of ISO C++20 features is pretty much frozen after the upcoming Cologne meeting, and modules are in.
Re:Catching use-after-move C++ bugs with Clang's consumed an...
by wyldfire on Thursday July 11, 2019 @08:44AM
(#20411041)
So the aforementioned death-on-arrival [1] was premature? Are there really implementations which end up faster as a result?
[1] https://vector-of-bool.github.io/2019/01/27/modules-doa.html