Closed stephenberry closed 3 weeks ago
This optimization was not well tested, is not generally useful (often indicates bad programming practices if necessary), and complicated the codebase.
The better solution is for users to reserve memory or to use std::unique_ptr/std::shared_ptr to avoid copying on resizing.
This optimization was not well tested, is not generally useful (often indicates bad programming practices if necessary), and complicated the codebase.
The better solution is for users to reserve memory or to use std::unique_ptr/std::shared_ptr to avoid copying on resizing.