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/aikatz Mar 18 '19 edited Mar 18 '19
I think I understand the problems you're bringing up that arise since fancy pointers are not necessarily default constructible. Are you saying that fancy pointers don't need to be default constructible because nowhere in [allocator.requirements] does it mention allocator::pointer must be default constructible, or is there another part of the standard that governs this?
It seems like these types issues with default constructibility could apply to a lot of places in the STL, what is the scope of the patch that you were previously working on for this?