Doesn't matter though because you aren't writing standards conforming C. You're writing whatever dialect your compilers support, and that's probably (module bugs) much better behaved than the spec suggests.

Or you're writing C++ and way more exposed to the adversarial-and-benevolent compiler experience.

The type aliasing rules are the only ones that routinely cause me much annoyance in C and there's always a workaround, whether if it's the launder intrinsic used to implement C++, the may_alias attribute or in extremis dropping into asm. So they're a nuisance not a blocker.

1. Generating enormous amounts of text

2. Persuading a mathematician to look closely at it

3. Announcing success if they conclude it is a proof

This is deeply disappointing relative to "chatgpt found a proof that isabelle verifies" or similar, especially the part where a mathematician spends (presumably hours) reading through the llm output.

With the exception of things that places like HN seems to consider worth reading, which is why I'm looking through the comments to this and others to find recommendations.

This setting will make no difference to whether your code is fed into their training set. "Oops we accidentally ignored the private flag years ago and didn't realise, we are very sorry, we were trying to not do that".

buffer_[head] = value;

head_.store(next_head, std::memory_order_release);

return true;

There's no relationship between the two written variables. Stores to the two are independent and can be reordered. The aq/rel applies to the index, not to the unrelated non-atomic buffer located near the index.

Also doesn't have fences on the store, has extra branches that shouldn't be there, and is written in really stylistically weird c++.

Maybe an llm that likes a different language more, copying a broken implementation off github? Mostly commenting because the initial replies are "best" and "lol", though I sympathise with one of those.

The rest of the infra is fine if that can be done. Array of batteries and/or capacitors at the supply point and draw continuously from the grid.

Most entertainingly run a diesel generator on site if that doesn't work out. Lines up well with basing them at the existing fuel stations, got the diesel supply already sorted out.

Put a bunch of solar near it when you can. Maybe sell back to grid, nice to have the extra capacity available.

All comes down to capital deployment at that point. Do the calculations on how much to charge for slow car charge vs fast charge, fallback to slow with an apology/discount when the infra is struggling etc.

Huge news. Iff the cars don't catch fire when plugged in.

You might think $10 an hour is fair. Or you might think $1000 an hour is fair. If the developers you're trying to contact can't guess where you are on pricing, they'll probably ignore you.