News for hackers. Stuff that matters.
Re:Announcing Rust 1.7 by Manishearth on Thursday March 03, 2016 @10:46PM (#11221953)
That 250K is additive, not multiplicative. Hello World, which might be 10K in C, will be 240K+10K=250K in Rust. A larger program that would be 2M in C would be 240K+2M in Rust; the significance of that 240K reduces when you write actual programs (instead of hello world).

The size is due to a statically linked stdlib (also jemalloc, which you can decide not to use) -- your C program is tiny because your system has a stdlib it can dynamically link to. Rust can do this too, it's just not the default since in most cases this additive extra binary size isn't a problem.

Being a systems language does mean we should forgo sensible defaults.

Re:Announcing Rust 1.7 by mystikal on Friday March 04, 2016 @01:29AM (#11222355)
In theory you could tell the compiler to identify and statically link only those functions needed to make printf work (or a conservative approximation thereof).
Re:Announcing Rust 1.7 by danieldk on Friday March 04, 2016 @01:48AM (#11222405)
Re:Announcing Rust 1.7 by Manishearth on Friday March 04, 2016 @04:35AM (#11222822)
Yeah, that's just running LTO (`-C lto`). This brings the binary size down a bit, thought you also need to opt out of jemalloc to get a good impact.
Re:Announcing Rust 1.7 by Manishearth on Friday March 04, 2016 @04:31AM (#11222819)
Edit: *doesn't