7,480 karma · joined September 13, 2011
meet.hn/city/51.0493286,13.7381437/Dresden
Socials: - bsky.app/profile/rurban - github.com/rurban ---
Only 3-4 compilers stayed secure in this regard, by either disallowing unicode names, or by using TR39.
What else is a high security riscs? All names, such as path names or user names on OS kernels, like filesystems. Filesystem or user db's with unicode support but without identifier support such as TR39 can also lead to security attacks. Apple once had at least HPFS which did normalization, but the recently gave up, because nobody cared. And Linus still calls garbage in, garbage out valuable. Even if the famous ssh attack used such an homoglyph attack to stay undetected.
Because here it is trivial to make them backwards compatible, by just using a PRE() and POST() macro which are empty pre-C++26.
The contracts_assert is either static or runtime, which the compiler can decide. Better than explicit static/asserts, which are either unnecessary or costly.
Just fire the naysayers (for refusing to work) and you have one problem less.
"By any means" is a current movie with the FBI case.
But the architecture is similar to kimi's mixture of experts, and we already have such an optimization for different experts swapped in from disc by antirez.