You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support --message-format=json for inline IDE hints with Rust Analyzer #571
Being able to pass --message-format=json would allow us to specify cargo gpu check --message-format=json as a check command and then the Rust Analyzer plugin would be able to read the output of this and show the errors and warnings within the IDE as underlines. This would be very useful for development.
Which is why I'd like to refactor the argument parsing of cargo-gpu to go from "everything can be passed as args" to "everything has to be configured in the Cargo.toml in the shader crate" and we parse (almost?) no args at all. Just forward all args to the underlying cargo implementation of <subcommand>, instead of reimplementing every single arg ourselves.
There's still a few people relying on passing cargo-gpu configuration via cmdline, so it'll be a breaking change for them, but I do think it's a necessity.
Activity
Firestar99 commentedon Jan 27, 2026
I see this issue being in the same bucket as
cargo gpu clippycannot pass--fixRust-GPU/rust-gpu#570: You can't pass ordinary arguments throughcargo gpu.Which is why I'd like to refactor the argument parsing of cargo-gpu to go from "everything can be passed as args" to "everything has to be configured in the
Cargo.tomlin the shader crate" and we parse (almost?) no args at all. Just forward all args to the underlying cargo implementation of<subcommand>, instead of reimplementing every single arg ourselves.There's still a few people relying on passing cargo-gpu configuration via cmdline, so it'll be a breaking change for them, but I do think it's a necessity.