Rustc is very tightly coupled with cargo. Nothing stops you from calling rustc yourself, but you basically need to reverse engineer what cargo is doing.
My reference for this is https://github.com/bazelbuild/rules_rust which needs to pass a bunch of CARGO_ envvars to get stuff to build, among various other required conventions.
This is a lot of words to say “I really don’t like the capitalised C”, which is a weirdly specific complaint and shockingly doesn’t actually make “cargo a mistake”.
That's a troll, isn't it? Not only can you compile directly with rustc, npm/yarn is definitely "institutionally required by default" as well. Also, there's no actual complaint here beyond "I don't like the vibes" - what's the actual issue?
4 comments
[ 1.8 ms ] story [ 19.0 ms ] threadMy reference for this is https://github.com/bazelbuild/rules_rust which needs to pass a bunch of CARGO_ envvars to get stuff to build, among various other required conventions.
This is a lot of words to say “I really don’t like the capitalised C”, which is a weirdly specific complaint and shockingly doesn’t actually make “cargo a mistake”.