mh7

7 ms·

31.
by mh7 5y ago
Not seen much point in rust for embedded for small MCU's that I target. All memory are statically "allocated" as global variables/buffers and never free'd, so there's no ownership or dangling references to worr
32.
by mh7 5y ago
You can't afford to waste cycles on O(n) strlen either.
33.
by mh7 6y ago
It's more to do with the fact that std::sort's definition is visible to the compiler and qsort() is not. Put qsort() code in stdlib.h, make it static and write a static intcmp() and you'll see the compiler inline that no prob
34.
by mh7 6y ago
Some of the rust versions calls C libraries for its heavy lifting (gmp, pcre) so I wouldn't take this too seriously.
35.
by mh7 6y ago
If you change the size or padding in a struct of course a dynamic library is gonna break every program using it, I'm not sure why intmax_t was singled out here.
36.
by mh7 6y ago
Look at all the software running on your computer right now, how much of it is open source? (Including OS, drivers, ssd/efi/cpu/misc controllers firmware). Email every website you visit and ask to get the source code. Go and
37.
by mh7 8y ago
Or you get something worse because you happened to be one of the few users of a niche feature that they decided the axe because they optimize for the telemetry data.
38.
by mh7 8y ago
Since the fixed width integer types are optional, and if available must be 8, 16, 32 and 64 bits (and two's compl) I don't think CHAR_BITS > 8 is allowed if stdint.h types are supported since sizeof(uint8_t) must be 1.