21st Century C++

Re:21st Century C++ by amluto on Sunday February 09, 2025 @04:03PM (#42993943)

> For std::vector it apparently just didn't occur to C++ people to provide the correct API, Bjarne Stroustrup claims the only reason to use a reservation API is to prevent reference and iterator invalidation. -shrug-

Do you mean something like vector::reserve_at_least()? I suppose that, if you don’t care about performance, you might not need it.

FWIW, I find myself mostly using reserve in cases where I know what I intend to append and when I will be done appending to that vector forever afterwards.

[ Parent | on HN ]

Re:21st Century C++ by tialaramex on Sunday February 09, 2025 @04:54PM (#42994457)

I'm not familiar with vector::reserve_at_least but assuming that's an API which reserves capacity without destroying the amortized constant time of the exponential growth built in to the type, yes, that.

[ Parent | on HN ]

Re:21st Century C++ by amluto on Monday February 10, 2025 @08:59AM (#43000381)

Oh, sorry, that’s an API that doesn’t exist. I was trying to understand what feature you wanted that didn’t exist.

[ Parent | on HN ]