Thread: STL functions to resize containers

You know that `std::vector<???>::erase(???)` calls a destructor, yet you claim that to resize is to reallocate and the distinction isn't useful?

An array is indeed some number of elements whether stored on the heap or not, but you seem to be either missing or ignoring the fact that memory allocated for elements isn't the same thing as the elements existing.

Yeah, I was ignoring it. I thought I was being helpful by not diving into gory details that I don't think get to the point of the question.

I needed a lecture on placement new just to prove how apparently wrong I am.

std::fstream * s(new std::fstream[8]);

8 objects exist.

(s + 7)->~fstream();How many elements of `std::fstream` exist?

7 objects exist.

new(s + 7) fstream();

8 objects exist.

You, at one point, have an array of only seven elements despite allocating memory for eight elements.

Right, now please tell me if sean contab will care or understand.

The distinction is useful for the STL containers in particular because of how each implies validity of iterators after the relevant operation.

Guess what we weren't talking about until Galik showed up.

But whatever... the gory details are out, please continue. I'm dumb, just like everybody apparently wanted. Thank you ........ you bye.

You chose to make misleading statements without simply stating "I'm glossing over the gory details, but..." or similar?

Apparently.


Hopefully you don't think too badly of me for it. I doubt I'll live it down now.

Now, please tell me if sean contab will be the only person to ever read the thread.


For example, do you think Galik will read the thread?


I only ask because the comments I took issue with was a response to Galik, not sean contab, who seems rather interested

If you really want to know the truth as I see it, I think the thread will die and sink to the depths only a word-for-word google query will find after we all shut up. Like the day you decide to link to the thread just to jog everyone's memory of that time we delved into pedantry. I don't think Galik will read the thread again since he brought up the topic I was "misleading" people about.

Well guess what, Galik apparently thought that further discussing the semantics of resizing arrays was appropriate.


You want to ding Galik for the necropost? Fine, but when did you become afraid of discussing semantically related issues?


If Galik had started a new thread, what would you have done?

You know things would have gone a lot better if you didn't teach people like you were ........ting on them off such a high cliff. How long are you going to berate me for an oversight which you heroically correc--wait, Galik did, that was Galik. The lecture is over professor, let me go home and do my homework, now, please.

Sorry, man, all I meant was that if you were just looking at destructors getting called, it might mean that a delete call happened. It's the whole duck-typing thing. If it quacks like a duck and sounds like a duck then it might just be. I assumed whiteflags was conflating destructors being called with a delete + new combo.