Fix exception-safety bug in folly::Try<T>::operator=()
Summary: If the value copy/move constructor threw an exception during copy/move assignment then the Try<T> object would not be left in the empty state. This could lead to double-deletion of resources, or referencing uninitialised memory. Reviewed By: yfeldblum Differential Revision: D9425118 fbshipit-source-id: 6639a0903258ecb031c26264f418fa8794519be3
Showing
Please register or sign in to comment