[PATCH] D34331: func.wrap.func.con: Unset function before destroying anything

[Eric Fiselier via Phabricator via cfe-commits]

EricWF requested changes to this revision.
EricWF added a comment.
This revision now requires changes to proceed.

@dexonsmith I'm not sure it's sane to allow reentrant behavior. Could you explain why you think it is? Should the copy assignment operator allow reentrancy as well?

However there is another bug here. `operator=(function&&)` doesn't correctly call the destructor of the functor. I'll fix that as a separate commit.


https://reviews.llvm.org/D34331