-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<ranges>
: Strengthen exception specification for _Defaultabox
#3762
<ranges>
: Strengthen exception specification for _Defaultabox
#3762
Conversation
|
@achabense is correct - we typically don't bother with "strengthened" comments for things that don't appear in the Standard. (For things that directly correspond to exposition-only functions, I think sometimes we do, but I forget specific examples.) |
There are also a lot of |
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
🦾
|
One non-defaulted move constructor for
_Defaultabox
is currently nevernoexcept
, which is probably a bug.So I decided not to add// strengthened
to that move constructor. Some similar constructors are made conditionallynoexcept
, and I think// strengthened
is suitable for them._Defaultabox
is used forjoin_view::_Iterator
andlazy_split_view
, while the standard wording usesoptional
andnon-propagating-cache
respectively. And thus I'm afraid that the exception specifications are not yet strong enough forlazy_split_view
. But further strengthening seems dangerous.