File tree Expand file tree Collapse file tree 1 file changed +6
-4
lines changed Expand file tree Collapse file tree 1 file changed +6
-4
lines changed Original file line number Diff line number Diff line change @@ -21,21 +21,23 @@ <h1>Exception reporting behavior</h1>
2121 < code > parallel_execution_policy</ code > , the execution of the algorithm terminates with an
2222 < code > exception_list</ code > exception. All uncaught exceptions thrown during
2323 the application of user-provided function objects shall be contained in the
24- < code > exception_list</ code > .
24+ < code > exception_list</ code > .< pre >
25+ </ pre >
2526
2627 < cxx-note >
2728 For example, the number of invocations of the user-provided function object in
2829 < code > for_each</ code > is unspecified. When < code > for_each</ code > is executed sequentially,
2930 only one exception will be contained in the < code > exception_list</ code > object.
30- </ cxx-note >
31+ </ cxx-note > < pre >
32+ </ pre >
3133
3234 < cxx-note >
3335 These guarantees imply that, unless the algorithm has failed to allocate memory and
3436 terminated with < code > std::bad_alloc</ code > , all exceptions thrown during the execution of
3537 the algorithm are communicated to the caller. It is unspecified whether an algorithm implementation will "forge ahead" after
3638 encountering and capturing a user exception.
37- </ cxx-note >
38-
39+ </ cxx-note > < pre >
40+ </ pre >
3941 < cxx-note >
4042 The algorithm may terminate with the < code > std::bad_alloc</ code > exception even if one or more
4143 user-provided function objects have terminated with an exception. For example, this can happen when an algorithm fails to allocate memory while
You can’t perform that action at this time.
0 commit comments