> I don't think any other languages have really solved this problem either but it is still an annoying problem.

> I don't think any other languages have really solved this problem either but it is still an annoying problem. As you say, this is not a problem with an ideal solution to draw upon. (languages are unavoidably different). From that perspective, I don't see any of these approaches as problems. If your project is mostly Rust with a little something else sprinkled in, use build.rs ("horrible" is an exaggeration IMO, it's merely not ideal, again, because there exists no ideal). If your project is mostly something-else with a little Rust sprinkled in, invoke `cargo build` from your build system, and again this is a perfectly adequate solution to a problem with no ideal solutions. If your project is extra-special, invoke rustc directly, and that's a deliberately supported use case. Hell, I use rustc directly sometimes just because I can. The bottom line is, Rust provides a best-in-class opinionated build system that is overwhelmingly used by the Rust ecosystem, with best-effort escape hatches for integrating into other projects. To say that Rust cannot "stand the idea that you might want to mix languages", as alleged by the person I originally replied to, is factually incorrect.

Posted by kibwen on Jan 20, 2023, 4:06 PM

Tags

• hackernews (Other)

Related issues

• The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
• (My comment is about detached houses).
• The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
• > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
• Why is there no comparison with FLUX 3 Image?
• > our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...