(but most often the comment is is just not updated or updated along with the code but without full understanding, which is what caused the bug that is the reason you are looking at the code in question)
> Note that, apart from contrived examples with deleted null checks, the current rules do not actually help the compiler meaningfully optimize code. A memcpy implementation cannot rely on pointer validity to speculatively read because, even though memcpy(NULL, NULL, 0) is undefined, slices at the end of a buffer are fine. [And if the end of the buffer] were at the end of a page with nothing allocated afterwards, a speculative read from memcpy would break
Is the only distinction the intention, though?
Because I saw some examples of industrial applications of cold welding, so I'm still not quite getting why cold welding isn't considered welding (I have been googling since my original comment, but not finding anyone making this same distinction).
I clicked on that Wiki link and it said cold welding is "welding process", and the hyperlink to the regular welding page includes solid-state welding, which mentions cold welding.
Normal welding is intentional application of heat to partially melt two parts at the seam, so that they "mix" in semi-liquid state and become one part when they solidify. Welding may or may not use a third material (solder) to aid the process.
It takes a considerable amount of depth in reasoning to see and reason about the patterns / problems / solutions.
Try doing a few of them by hand to see what I mean.
Simulated worlds are complex enough to hide their own flaws just like LLMs are complex enough to lead us to believe they can reason when most of the time they are pattern matching.
Side note: there is a trivial case where authentication is reduced to “whoever is physically holding/interacting with the system”. This is when either the operation to be authorized is relatively low risk (changing the channel on the TV with the line-of-sight IR remote control) or when you’re depending on physical security controls to prevent access to people who shouldn’t be doing the thing, e.g. requiring data center technicians to badge in before they can go into the server room and start disconnecting things.
Have you found any LLMs or coding agents that work well with Haxe? It might be a bit too niche for us (again, not sure yet), but I'd be very curious to see what they do well!