Wait, no. set<int> would have avoided the leak/bloat completely. multiset<int> would have still bloated with unbound memory use. But either template would find() so efficiently that the bug would never have been noticed as CPU use.
« Back to merge proposal
Wait, no. set<int> would have avoided the leak/bloat completely. multiset<int> would have still bloated with unbound memory use. But either template would find() so efficiently that the bug would never have been noticed as CPU use.