Author: prazek Date: Fri Mar 3 11:16:11 2017 New Revision: 296888 URL: http://llvm.org/viewvc/llvm-project?rev=296888&view=rev Log: [clang-tidy] Yet another docs fixes
Modified: clang-tools-extra/trunk/docs/clang-tidy/checks/modernize-use-emplace.rst Modified: clang-tools-extra/trunk/docs/clang-tidy/checks/modernize-use-emplace.rst URL: http://llvm.org/viewvc/llvm-project/clang-tools-extra/trunk/docs/clang-tidy/checks/modernize-use-emplace.rst?rev=296888&r1=296887&r2=296888&view=diff ============================================================================== --- clang-tools-extra/trunk/docs/clang-tidy/checks/modernize-use-emplace.rst (original) +++ clang-tools-extra/trunk/docs/clang-tidy/checks/modernize-use-emplace.rst Fri Mar 3 11:16:11 2017 @@ -69,7 +69,7 @@ exception safe. In this case the calls o This is because replacing it with ``emplace_back`` could cause a leak of this pointer if ``emplace_back`` would throw exception before emplacement (e.g. not -enough memory to add new element). +enough memory to add a new element). For more info read item 42 - "Consider emplacement instead of insertion." of Scott Meyers "Effective Modern C++". @@ -79,14 +79,15 @@ The default smart pointers that are cons other classes use the :option:`SmartPointers` option. -Check also fires if any argument of constructor call would be: +Check also doesn't fire if any argument of the constructor call would be: - - bitfield (bitfields can't bind to rvalue/universal reference) + - a bit-field (bit-fields can't bind to rvalue/universal reference) - - ``new`` expression (to avoid leak) or if the argument would be converted via - derived-to-base cast. + - a ``new`` expression (to avoid leak) -This check requires C++11 of higher to run. + - if the argument would be converted via derived-to-base cast. + +This check requires C++11 or higher to run. Options ------- _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits