You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current Networking TS (N4734) basic_waitable_timer::cancel() is not noexcept. Is this because of memory allocation while canceling or was the noexcept simply forgotten?
The question is probably more important for expires_at(). I assume it throws under the same circumstances as cancel(). When calling expires_at() I often know that there are no pending async_wait's. Is it safe to call expires_at() without expecting an exception then? If yes, a hint on that in the TS would be very useful.
In the current Networking TS (N4734)
basic_waitable_timer::cancel()
is notnoexcept
. Is this because of memory allocation while canceling or was thenoexcept
simply forgotten?The question is probably more important for
expires_at()
. I assume it throws under the same circumstances ascancel()
. When callingexpires_at()
I often know that there are no pendingasync_wait
's. Is it safe to callexpires_at()
without expecting an exception then? If yes, a hint on that in the TS would be very useful.I asked a similar question on Stackoverflow.
The text was updated successfully, but these errors were encountered: