There is a kind of developer who likes to take the WRONG DESIGN and then program it in C++ and then tell us what's wrong. I see this on a regular basis. Shows a lack of analytic thinking.
In the current case, std::unique_ptr() is the wrong tool. It was not built for that purpose.
Use shared_ptr. Recommended usage of std::unique_ptr
So, to use std::unique_ptr() define it in a scope!!! and stop the messing by trying to conjure up crap examples.
If schools start graduating people with rust experience, the writing is on the wall for C++. Shifting school curriculum takes a big reason. Maybe a hit indie game, maybe some other killer app. I don't think servo is the one.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.