More to the point, I think, when I asked the same question in the #include<c++> server, one of the answers I got was that as a concurrency framework, if asio doesn't perform proper synchronization, then it is fundamentally broken ;)

I actually looked into this a few months ago! The closest thing I could find was the page on concurrency hints, which documents scheduler and reactor configuration options. Notably the "scheduler.locking" option is true by default, and what that entails is documented there.

Ah, in that case, yeah that's bad 😬

Quote tweets show up as "blocked" when the quoted person blocks the quoter. You can see this even if you've never interacted with the blocked person, it's pretty frequent.

It's not quite complete yet, but it's getting there. All that's left is classes, and a proper GC if I'm feeling up to it.

Basically, United States Digital Service (USDS) was renamed and repurposed to United States DOGE Service.

www.whitehouse.gov/presidential...

At first it looked like a bot account gone haywire, but no, he's all too real. A search of his name yielded this.

www.wkbn.com/news/local-n...

Hey! I started reading Crafting Interpreters last night and followed you just this morning :)