Ancestors

Written by Björkus "No time_t to Die" Dorkus on 2025-01-24 at 04:04

Mmmmmnnnn, data.... https://thephd.dev/the-big-array-size-survey-for-c-results

=> More informations about this toot | More toots from thephd@pony.social

Toot

Written by James Henstridge on 2025-01-24 at 09:26

@thephd Most of the pain of the _Keyword+header option comes from writing headers for libraries. You need to treat the keyword as reserved from day one in case a user includes the header, and are stuck using the underscore version of the keyword if you don't want to pollute the namespace for callers.

From that perspective, I can see the desire to have the nice to use keyword now.

=> More informations about this toot | More toots from jamesh@aus.social

Descendants

Written by Björkus "No time_t to Die" Dorkus on 2025-01-24 at 12:24

@jamesh The library bit bites me so much, but at this point I just stopped caring and just include the headers anyways. They're effectively keywords due to text-based inclusion with headers, and I'm not gonna think too hard about it.

=> More informations about this toot | More toots from thephd@pony.social

Written by Alex Celeste on 2025-01-24 at 17:41

@jamesh it's related to a problem that has been called out a couple of times before when adding APIs

1. Standard reserves namespace

2. Community implements functionality outside the reserved namespace

3. Standard adopts functionality

4. red_blue_button.png do we trample all over their namespace, or introduce a competing different spelling nobody is going to use??

it's a namespace-reservation-treadmill

@thephd

=> More informations about this toot | More toots from erisceleste@tech.lgbt