this post was submitted on 02 Apr 2026
156 points (99.4% liked)
Programming
26369 readers
161 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The only reason to do this is if you're directly integrated Rust into an existing build system (e.g. Bazel). It's not going to help with this problem at all.
No, it wont. I wasn't suggesting someone should use rustc directly. You're already using Rust, so using cargo isn't adding to the supply chain.
That being said, there was one time I needed to use rustc directly. We had an assignment that needed to be compilable from a single source file. I couldn't bundle a Cargo.toml, so I gave a build script that used rustc directly.