bgloyer
bgloyer
Can we use 'valid-but-uspecified' until it is offically settled? I don't think it is practical to have the rule stronger than what the stl types do. Any type with an...
This was mentioned in Issue #1781 for shared_ptr
The wording of this one is a little confusing. The text under 'Reason' implies that ````x = std::move(x)```` should never change ````x````. However the stl containers don't give that guarnatee...
I think the rule is good but agree that the enforcement should be relaxed in cases where a number represents itself and is impossible to change. For example a triagle...
Since cloning is covered in C.130, can the cloning example be removed from C.21. Maybe replace it with an example that has copy deleted and move defined to show that...
What should an example for R.36 (passing ```const shared_ptr&```) show? Should it conditioanally take ownership? Would passing by const ref violate F.15 (prefer simple passing)?
I think almost the same effect can be acheived by passing the shared_ptr by value and having the caller std::move() its shared_ptr when calling the function. That has the advantage...
I tried it on python 2.7 and 3.7 which both worked, not sure what the problem in the build is.
This is a good change. Another exception would be using large objects that you don't want local: const auto huge = make_unique(3); Basing the enforement around 'const unique_ptr' seems to...
I got this too when hooking up to Gentoo's package tree