Reply to thread

Message: [QUOTE="Jeff Schwab, post: 3451569"] Right, but what's the relevance? I don't understand what you mean. I was pointing out that in: m[k] = v; The map first has to default-construct the value (assuming this is the first time the map entry has been accessed), then assign to it. One could instead check for the correct position of the value with lower_bound (I mistakenly said map::find), then use that iterator as a hint to insert the new value. This way, the value in the map can be copy-constructed in the first place, rather than default-constructed, then assigned. [/QUOTE]