I would add to that, replace #include with a proper module system that fixes the encapsulation and redundant parsing problems once and for all.
It's 2025 and C++ modules still aren't suitable for real world use yet despite being standardized 5 years ago.
Additionally standardize the ABI up front so that different compilers can interoperate. Make namespaces native to the object file format.
Also, explicitly standardize a compiler optimization mode that does not try to exploit UB in eldritch ways that break basic assumptions about how the machine works for 1% performance gain. I get that's an undecidable problem so it's ok if some extra annotations (call them "attributes" and write them [[like this]]) are needed here for explicit optimizer hints.
No doubt Nintendo was involved in the lobbying effort for this. Back in the 80s they successfully pushed to amend Japanese copyright law to ban game rentals.
Also, NaN is the only value in JS that isn't === to itself, so if for some reason you want to test for strict value identity with the value NaN of type number, that's one way to do it:
Looks like an early stage, immature project, but it's a neat concept.
It seems Windows Defender flags the zip download as a trojan. Likely false positive since scans on the unzipped exe (Defender and virustotal) come back clean.
I'd suggest providing a way to disable the builtin schemas in case someone wants to use it for more tech things as opposed to business things.
Anyone working in government, banking, or healthcare is still out of luck since the likes of Claude and GPT are (should be) off limits.
reply