3 ms·
If memory safety needs this level of fuckery to get going, it's not worth it for vast majority of software. Maybe stick to a GCed language until we can come up
by dingi 3y ago
If memory safety needs this level of fuckery to get going, it's not worth it for vast majority of software. Maybe stick to a GCed language until we can come up with a sane way to do it. These examples look cryptic as hell.
- steveklabnik 3y agoIt's cryptic because it is a reduced test case to show off a bug. 99.9% of code doesn't look like this. Just because "int ((foo)(void ))[3]" is a valid C declaration doesn't mean that all of C code looks like that.
- pcwalton 3y agoThis is basically the Rust equivalent of the obfuscated C code contest and indicates little to nothing about the actual Rust people write.
- datadeft 3y ago> this level of fuckery to get going C++ has the same level of fuckery without memory safety. I don't think there is an extreme level of fuckery in Rust. I wish they got more influence from the ML languages than C++ but it is not unbearable.
- 0x457 3y agoIt's a level of fuckery required to trigger a compiler bug. You don't see code like this in real code bases.