Mirrors/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2025-12-18 05:04:41 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

E.16: Fix inconsistent description (#2209)

Browse Source
This commit is contained in:
boyeong-jeon
2024-07-02 22:19:37 +09:00
committed by GitHub
parent 5ff92185f3
commit 50afe0234c
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
CppCoreGuidelines.md
View File

@@ -16363,7 +16363,7 @@ The standard library assumes that destructors, deallocation functions (e.g., `op
* `swap` functions must be `noexcept`. * `swap` functions must be `noexcept`.
* Most destructors are implicitly `noexcept` by default. * Most destructors are implicitly `noexcept` by default.
* Also, [make move operations `noexcept`](#Rc-move-noexcept). * Also, [make move operations `noexcept`](#Rc-move-noexcept).
* If writing a type intended to be used as an exception type, ensure its copy constructor is not `noexcept`. In general we cannot mechanically enforce this, because we do not know whether a type is intended to be used as an exception type. * If writing a type intended to be used as an exception type, ensure its copy constructor is `noexcept`. In general we cannot mechanically enforce this, because we do not know whether a type is intended to be used as an exception type.
* Try not to `throw` a type whose copy constructor is not `noexcept`. In general we cannot mechanically enforce this, because even `throw std::string(...)` could throw but does not in practice. * Try not to `throw` a type whose copy constructor is not `noexcept`. In general we cannot mechanically enforce this, because even `throw std::string(...)` could throw but does not in practice.
##### Enforcement ##### Enforcement