4 ms·
The build system issue isn't inherent to Rust or to large organizations. Even in a startup, we have a polyglot development with a separate build tool in additio
by kccqzy 7y ago
The build system issue isn't inherent to Rust or to large organizations. Even in a startup, we have a polyglot development with a separate build tool in addition to the language-specific build tool. We ended up doing much of the same things: use the language-specific build tool to generate artifacts which are then consumed by the normal build tool.
- monocasa 7y agoA slight difference is that Rust really wants to be the top level compiler. More than a lot of languages, even C++, it really relies on link time optimization to get the perf you'd expect.
- kccqzy 7y agoIn that case just print the command line cargo would've used to do the linking and let a different consume that and make changes. That's an easy case.
- hope-striker 7y agoHow this is more true of Rust than modern C++?
- SamReidHughes 7y agoMost "modern" C++ involves template metaprogramming of a sort that is in header file, so the modern aspect doesn't stand to increase the need for LTO that much. I would imagine that Rust programs benefit from LTO by removing static assertions necessary for memory safety that C++ programs simply omit, and by unraveling functional style code that Rust programs often get shoehorned into. Or maybe not, but that's one non-LTO that's needed.
- bsder 7y ago> The build system issue isn't inherent to Rust or to large organizations. That may be true, but even the big boys can't converge, and they all have their own build systems. Attempting to add/remove features from cargo/rust when even the big companies can't agree as to what is most important in a build system seems like a path to disaster. The big boys aren't always right (see: Gradle/Groovy).