tmp/tmpsu7kw_wk/{from.md → to.md}
RENAMED
|
@@ -1,15 +1,15 @@
|
|
| 1 |
### [[except]]: exception handling <a id="diff.cpp14.except">[[diff.cpp14.except]]</a>
|
| 2 |
|
| 3 |
**Change:** Remove dynamic exception specifications. **Rationale:**
|
| 4 |
Dynamic exception specifications were a deprecated feature that was
|
| 5 |
complex and brittle in use. They interacted badly with the type system,
|
| 6 |
-
which became a more significant issue in this
|
| 7 |
-
|
| 8 |
-
|
| 9 |
-
|
| 10 |
-
|
| 11 |
-
|
| 12 |
-
|
| 13 |
-
|
| 14 |
-
|
| 15 |
|
|
|
|
| 1 |
### [[except]]: exception handling <a id="diff.cpp14.except">[[diff.cpp14.except]]</a>
|
| 2 |
|
| 3 |
**Change:** Remove dynamic exception specifications. **Rationale:**
|
| 4 |
Dynamic exception specifications were a deprecated feature that was
|
| 5 |
complex and brittle in use. They interacted badly with the type system,
|
| 6 |
+
which became a more significant issue in this revision of C++ where
|
| 7 |
+
(non-dynamic) exception specifications are part of the function type.
|
| 8 |
+
**Effect on original feature:** A valid C++14 function declaration,
|
| 9 |
+
member function declaration, function pointer declaration, or function
|
| 10 |
+
reference declaration, if it has a potentially throwing dynamic
|
| 11 |
+
exception specification, is rejected as ill-formed in this revision of
|
| 12 |
+
C++. Violating a non-throwing dynamic exception specification calls
|
| 13 |
+
`terminate` rather than `unexpected`, and it is unspecified whether
|
| 14 |
+
stack unwinding is performed prior to such a call.
|
| 15 |
|