News for hackers. Stuff that matters.
Re:Rust: Not So Great For Codec Implementing by pjmlp on Wednesday August 02, 2017 @03:03AM (#14908525)
A current problem with " should just use crates" is that cargo only works with source code dependencies, not binary libraries.

So each new crate added to your project ends up increasing the overall build time, which gets exponentially bad if you happen to add a dependency to a crate than happens to have a big dependency list.

I have a very basic word counting application with a GUI written in Gtk-rs, a fresh build straight out of "git clone" takes a few minutes, mainly thanks to Pango.

Re:Rust: Not So Great For Codec Implementing by Sean1708 on Wednesday August 02, 2017 @04:21AM (#14908825)
> So each new crate added to your project ends up increasing the overall build time,

That's only a problem the first time you compile though, isn't it?

Re:Rust: Not So Great For Codec Implementing by pjmlp on Wednesday August 02, 2017 @04:42AM (#14908935)
A problem that I usually don't have with C++[0], Java[1] or .NET[2], thanks to the build systems support for binary libraries.

[0] - I eschew header only libraries, only if there is no technical way around them (e.g. templates).

[1] - I can AOT compile with Excelsior JET, IBM J9, JamaicaVM, PTC, , Oracle Java 9 (Linux x64 for the time being), ...

[2] - I can AOT compile with Mono, NGEN, .NET Native, CoreRT, IL2CPP, ...

Re:Rust: Not So Great For Codec Implementing by Sean1708 on Wednesday August 02, 2017 @06:40AM (#14909458)
I'm not saying it isn't a problem, I just wanted to know if I was correct in thinking that it is only a problem the first time you compile each crate (or rather each version of each crate, I think).
Re:Rust: Not So Great For Codec Implementing by pjmlp on Wednesday August 02, 2017 @07:03AM (#14909554)
I see.

Yes, it is a problem when you do a clean build, or when you have common crates across projects, because cargo doesn't have a concept of build cache.

You can try to workaround it by setting all target directories to same one via target-dir in your .cargo/config file, but there is no guarantee that the crate won't get rebuild.