Implement P2530R3, Hazard Pointers
Matteo Nicoli
matteo.nicoli001@gmail.com
Mon Nov 24 21:58:26 GMT 2025
Hi Johnathan,
Sorry for the delay, but it’s been a busy month. Anyway, I read the documents — in particular those that concerned the code style — and started implementing it.
I am following the other std headers, with the internals under bits/name.h. By the end of the week I should have a draft of the implementation. I read in some other mail threads that it would be better to submit the patches here in txt format, is it correct?
Thank you for your time,
Matteo
> On Oct 9, 2025, at 10:41 AM, Jonathan Wakely <jwakely@redhat.com> wrote:
>
> On Wed, 8 Oct 2025 at 23:32, Matteo Nicoli wrote:
>>
>> Hi everybody,
>>
>> I am following up on the discussion started in this ticket regarding the implementation of Hazard pointers from this C++26 standard proposal. Is anyone already working on this? If not, I would like to start sketching out a design for this implementation so that we can discuss it here.
>
> Hi, thanks for your interest in contributing this feature!
>
> I don't think anybody has said anything about working on it, so you
> won't be duplicating work. If somebody is already working on it
> silently in private somewhere, I hope they'll reply to this thread and
> let you know. Otherwise, assume you have a blank slate to work from.
>
> Regarding the logistics of contributing to libstdc++, please see the
> following links. The "legal prerequisites" part of the first link is
> important, the rest might be useful later down the road:
> https://gcc.gnu.org/contribute.html
> https://gcc.gnu.org/onlinedocs/libstdc++/manual/appendix_contributing.html
> https://gcc.gnu.org/onlinedocs/libstdc++/manual/source_organization.html
> https://gcc.gnu.org/onlinedocs/libstdc++/manual/source_code_style.html
> (this needs some modernization, but is still mostly accurate)
> https://gcc.gnu.org/onlinedocs/libstdc++/manual/test.html
>
> That might seem like a lot of information, but you won't need it all
> and people on this list will be happy to help with it. The harder part
> and the more important part will be just designing and implementing
> the feature, so you should focus on that not the logistics.
>
More information about the Libstdc++
mailing list