1. Changelog| thephd.dev
… Let’s talk about something that has haunted me for over a year now.| The Pasture
Surprise! Just because we released C23, doesn’t mean we’ve stopped working on C as a whole! There is a TON of things to do, and we have absolutely been busy working on things!| The Pasture
After the Graz, Austria February 2025 WG14 Meeting, I am now confident in the final status of the defer TS, and it is now time.| The Pasture
Happy New Year! It is time report the results of the Array Size Operator survey and answer some comments people have been asking for!| The Pasture
New in C2y is an operator that does something people have been asking us for, for decades:| The Pasture
N3366 - Restartable Functions for Efficient Character Conversions has made it into the C2Y Standard (A.K.A., “the next C standard after C23”). And one of my longest struggles — the sole reason I actually came down to the C Standards Committee in the first place —| The Pasture
The first two meetings of C after C23 was finalized are over, and we have started working on C2y. We decided that this cycle we’re not going to do that “Bugfix” followed by “Release” stuff, because that proved to be a REALLY bad idea that killed a ton of momentum and active contributors during the C11 to C17 timeframe. So, this time, we’re hitting both bugfixes AND features so we can make sure we don’t lose valuable contributions and fixes by stalling for 5 to 6 years again. So,...| The Pasture
Constant integer-typed (including enumeration-typed) object declarations in C that are immediately initialized with an integer constant expression should just be constant expressions. That’s it.| The Pasture
Ever since I finished publishing the “defer” paper and successfully defended it on its first go-around (it now has tentative approval to go to a Technical Specification, I just need to obtain the necessary written boilerplate to do so), an old criticism| The Pasture
I received a few complaints that #embed was difficult to implement and hard to optimize. And, the people making these claims| The Pasture
Following up from the last post, there is a lot more we need to cover. This was intended to be the post where we talk exclusively about benchmarks and numbers. But, I have unfortunately been perfectly taunted and status-locked,| The Pasture
I will no longer be speaking at RustConf 2023 about A (Possible) Future for Compile-Time Programming.| The Pasture
Previously, an article made the rounds concerning Undefined behavior that made the usual Rust crowd go nuts and the usual C and C++ people get grumpy that someone Did Not Understand the Finer Points and Nuance of Their Brilliant Language. So, as usual, it’s time for me to do what I do best| The Pasture
C and C++ as languages have a few things separating them from each other, mostly in their minute details and, occasionally, larger feature sets like designated initializers. But there is a disturbingly high amount of C++ that can simply do C’s job far better than C| The Pasture
Last time we talked about encodings, we went in with a C++-like design where we proved that| The Pasture
It’s That Blog Post. The release one, where we round up all the last of the features approved since the last time I blogged. If you’re| The Pasture
It happened. Nearly 5 years of paper writing, being snuck Committee Meeting notes on the DL until I could access them myself and absolve my co-conspirators of their sins, 5 different implementations/patches later, I can| The Pasture
The Committee says these things do not exist. The Committee says these things are invisible, not our business, and not something we can or should talk about.| The Pasture
A tweet popped off, and I kept getting asked a lot of questions about what is or is not in C23. So,| The Pasture
After that first Firebrand of an article on Application Binary Interface (ABI) Stability, I’m not sure anyone expected this to be the title of the next one, huh? It seems especially bad,| The Pasture