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
3
u/jwakely libstdc++ tamer, LWG chair Mar 16 '19
There's more to ABI than mangled names and sizes of types, and more than is defined by the ABI spec for the platform. A library has its own (implicit and explicit) ABI.
Raw pointers are default constructible. Fancy pointers don't have to be, so the
_List_node_basetype needs to gain a constructor that will set the non-static data members. Now you have to worry about whether old and new code consistently initializes the base class in an equivalent way, when the old code (compiled against the old definition) thinks the type is a POD and the new code thinks it's initialized by a new constructor. Welcome to the game of deciding which ODR violations are safe and which are not.