Closed GuillaumeDua closed 3 years ago
The types already have a strong exception guarantee. However, making a no-throw guarantee seems ideal here. Simply marking watch_result
's move-assignment operator as noexcept
would result in a compilation error, as get_result
is not no-throw move-assignable. The fix here is to rule-of-6 all the types.
Please consider the strong exception guarantee, e.g non-throwing move-assignement/move-assignement.
Current code :
So
Please consider using
noexcept
for strong exception garantee :