4 ms·

You should open an issue with whoever packages that library. Nobody expects library consumers to be experts in how to build libraries. But this isn't any diff

You should open an issue with whoever packages that library. Nobody expects library consumers to be experts in how to build libraries. But this isn't any different that depending on a C library, and discovering that the Makefile they are using compiles it with -O0, and makes it super slow. To a non-C programmer, flipping -O0 to -O3 is wizardry. --- Point being, you are not a rust programmer, and the defaults that are good for "development" are not good for "shipping" and therefore no good for you. If your library doesn't do this right, open a bug. The library can override this, and a package that builds it should override this.

user-the-name 6y ago
No, this is a fully optimised release build, built according to official instructions. Rust code is just very big. This seems to come with the territory.
- volta83 6y ago
  > Rust code is just very big. This seems to come with the territory. As someone that uses Rust every day to program STM32s with 128KB of space... i... disagree... Rust is the only high level language I know that allows me to customize the language run-time at will, allowing me to provide my own unwinding, threading, memory allocation, ... runtimes, to be able to program tiny machines as if I was just programming any normal one. With other languages either I can use the standard library implementation, or I can't use the standard library and some language features at all. With Rust, I can't use the standard library implementation for desktops, but I can just swap its backend by an embedded one, and am still able to re-use all the high level code, libraries from crates.io that use it, etc.