I'd guess that majority of such binary-only libraries use C ABI interfaces. The entire Windows ecosystem of COM modules works on top of C ABI's.
This is interesting because i'm writing quite a bit of embedded Rust, and i always run into limitations of very barebones const generics. I always wish they'd have half the expressiveness of C++ constexpr and templates.…
[dead]
Honestly i have a far easier time finding working no-std libraries for anything i need on embedded Rust compared to embedded C++. Arduino ecosystem is an exception, but that's not necessarily something i'd put in…
I actually remember reporting a crypto bug way back through a similar program in Win98, where certain keys would not work if the highest bit was set in the key material. It got fixed
Whats wrong with Python maintainability ? As long as you CI and lint properly, i haven't seen much issues
I'd guess that majority of such binary-only libraries use C ABI interfaces. The entire Windows ecosystem of COM modules works on top of C ABI's.
This is interesting because i'm writing quite a bit of embedded Rust, and i always run into limitations of very barebones const generics. I always wish they'd have half the expressiveness of C++ constexpr and templates.…
[dead]
[dead]
Honestly i have a far easier time finding working no-std libraries for anything i need on embedded Rust compared to embedded C++. Arduino ecosystem is an exception, but that's not necessarily something i'd put in…
I actually remember reporting a crypto bug way back through a similar program in Win98, where certain keys would not work if the highest bit was set in the key material. It got fixed
[dead]
Whats wrong with Python maintainability ? As long as you CI and lint properly, i haven't seen much issues