Second half of the February-March C meeting is over.
Surprisingly, a few things I expected to get spiked into the dirt made it through, and a lot of it was inversely proportional to the amount of effort I put in compared to the first half of the meeting:<li>defer TS approval to finally publish (after I fix all the godawful typos/thinkos)</li><li><code>const</code> integers are really Constant Expressions (e.g. usable in static assert and shit)</li>
Progress was made on the _Any_func* paper, but in order for it to proceed I have to remove everything related to "representation affinities" and leave the actual bit representation -- and whether they convert cleanly with memcpy or otherwise -- as a black box instead. This readily takes my most important use case and shoots it in the back of the head but, whatever. Something something compromise. Varying levels of Tentative Support for everything else, though apparently there's serious objections to printing an _Any_func* which seems... like a very bizarre part of the thing to be against. Maybe i can do a better job of convincing people of that next time.
Thread Attributes made forward progress. People keep trying to kill off the wide string and UTF-8 string versions of the "set name". I don't know why they keep doing that, because that just means certain platforms (not just Windows, but CERTAINLY Windows) will be utterly fucked. We did agree to keep THRD_NAME_*_MAX, where * is either nothing or SIZE.
Björkus "No time_t to Die" Dorkus
npub1yc…4j9p5
2026-03-14 15:36:43 UTC
Author Public Key
npub1ycvj968p0kv4y48g4tvmph87vz0vc3sh9tzxmq2acmwgwzv4v5pq94j9p5Seen on
wss://relay.momostr.pinkPublished at
2026-03-14 15:36:43 UTCEvent JSON
{
"id": "d62408aca7f27fe7263e938972f908a5d5cf488dc08d61bf835a5b10b3616286",
"pubkey": "261922e8e17d995254e8aad9b0dcfe609ecc46172ac46d815dc6dc8709956502",
"created_at": 1773502603,
"kind": 1,
"tags": [
[
"proxy",
"https://pony.social/@thephd/116228257656873715",
"web"
],
[
"proxy",
"https://pony.social/users/thephd/statuses/116228257656873715",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://pony.social/users/thephd/statuses/116228257656873715",
"pink.momostr"
],
[
"-"
]
],
"content": "Second half of the February-March C meeting is over.\n\nSurprisingly, a few things I expected to get spiked into the dirt made it through, and a lot of it was inversely proportional to the amount of effort I put in compared to the first half of the meeting:\u003cli\u003edefer TS approval to finally publish (after I fix all the godawful typos/thinkos)\u003c/li\u003e\u003cli\u003e\u003ccode\u003econst\u003c/code\u003e integers are really Constant Expressions (e.g. usable in static assert and shit)\u003c/li\u003e\n\nProgress was made on the _Any_func* paper, but in order for it to proceed I have to remove everything related to \"representation affinities\" and leave the actual bit representation -- and whether they convert cleanly with memcpy or otherwise -- as a black box instead. This readily takes my most important use case and shoots it in the back of the head but, whatever. Something something compromise. Varying levels of Tentative Support for everything else, though apparently there's serious objections to printing an _Any_func* which seems... like a very bizarre part of the thing to be against. Maybe i can do a better job of convincing people of that next time.\n\nThread Attributes made forward progress. People keep trying to kill off the wide string and UTF-8 string versions of the \"set name\". I don't know why they keep doing that, because that just means certain platforms (not just Windows, but CERTAINLY Windows) will be utterly fucked. We did agree to keep THRD_NAME_*_MAX, where * is either nothing or SIZE.",
"sig": "6893948c821c6b6fd14aa9e747d0bc6332af83edfca69735ff34ba4c4e5af073b12838eace69ccc6296e7376680958d3c58da49ad54dc4b75a203fad64cbedb8"
}