Closed dvdfreitag closed 7 years ago
The copy constructors for neither::Either and neither::Maybe have been updated to use proper copy-construction using a placement new.
neither::Either
neither::Maybe
Note: These values won't need to be deleted manually, but they will probably need to be manually destroyed, which the library already does.
Thx for your PR!
For reference, the stackoverflow discussion leading to this change: std::future<neither::Either<int, std::string>> segmentation fault
std::future<neither::Either<int, std::string>>
The copy constructors for
neither::Either
andneither::Maybe
have been updated to use proper copy-construction using a placement new.Note: These values won't need to be deleted manually, but they will probably need to be manually destroyed, which the library already does.