The mimalloc_ruust library is marked as #![no_std], yet libmimalloc-sys is not marked as #![no_std] so no_std users of mimalloc_rust will pull in the std library as a result. This seems like a small oversight.
My specific use-case for this change is because I wish to create a library that does not link to std for a smaller size, but that still requires allocations.
I did not thoroughly check if this will adversely affect other end users, I'm hoping CI/CD will catch these.
The
mimalloc_ruust
library is marked as#![no_std]
, yetlibmimalloc-sys
is not marked as#![no_std]
sono_std
users ofmimalloc_rust
will pull in thestd
library as a result. This seems like a small oversight.My specific use-case for this change is because I wish to create a library that does not link to
std
for a smaller size, but that still requires allocations.I did not thoroughly check if this will adversely affect other end users, I'm hoping CI/CD will catch these.