Closed HolyBlackCat closed 1 year ago
Now that I'm thinking about it, this is a breaking change for those who copy a newly constructed b2World
, like you did in tests (which is safe, unlike copying worlds with something inserted into them). I don't think this is a big deal, since there's a workaround (wraping one in unique_ptr
or optional
), so I wouldn't bother writing move ops.
not accepting PRs, but I'll keep the issue open
Fixes #711
I went over all classes with custom destructors, and
=delete
d or=default
ed their copy operations. In cases where that would remove the default constructor, I added it back.