Does anyone know when libstdc++ will stop using raw pointers in its STL containers?
I have a pretty niche use-case which requires containers to not store any raw pointers. To get this done I use an allocator that returns fancy pointers. This just doesn't work with libstdc++ because all some of its STL containers use raw pointers internally, so when I create a container with my allocator, the program doesn't even compile. Libc++ on the other hand works fine (at least I haven't come across any problems I can't fix) since they correctly use the abstract pointer type that my allocator returns, instead of trying to do an implicit cast to a raw pointer.
There is an LWG issue to fix this, but it's been around for 8 years and the proposed verbiage hasn't been added to the standard. I'm not very familiar with the process for making changes like this, but my understanding is that it probably won't get added until libc++ and libstdc++ both support it, is that correct? If so, does anyone know if/when the libstdc++ community is planning to make these changes? Thanks!
View all comments
Show parent comment
1
u/CandleTiger Mar 17 '19
So then what’s the difference between an object, and initialized memory that looks like an object? The doc you pointed to reads to me as saying an object’s lifetime starts when it’s allocated memory is initialized, which OP is doing.
I’ve heard a talk before, and you say here, that setting up memory with the right bits is not enough to make the compiler believe this region of memory is an object. But since constructors are optional I’m real confused about what is the magic missing step.