------- Additional Comments From pcarlini at suse dot de 2004-11-26 10:58
-------
Actually, just moving down the resize is not ok, since __n and __first would
need
to be recomputed too, with a non-trivial overhead in case of insert. Also, the
memory doubling happens only when one of the thresholds is encountered, not in
the common case. Add to this that these are basically legacy and non-portable
facilities (new ISO-mandated unordered containers will be provided soon). All
in all, better not touching find_or_insert, sorry.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18633
