Problem
Currently, hurry cross assumes that if the first argument starts with -, we're running against cross directly and should passthrough. However, this misses cases like:
cross --locked build --target x86_64-unknown-linux-gnu
In this case, --locked is the first argument but build should still be accelerated.
Context
This is the same issue that exists for hurry cargo - see the similar FIXME in cmd/cargo.rs.
Reference: PR #254 review comment from @elldritch
Suggested approach
Parse global flags first, then dispatch to the appropriate subcommand handler. This would allow acceleration to work correctly for commands like cross --locked build.
🤖 Generated with Claude Code
Problem
Currently,
hurry crossassumes that if the first argument starts with-, we're running againstcrossdirectly and should passthrough. However, this misses cases like:In this case,
--lockedis the first argument butbuildshould still be accelerated.Context
This is the same issue that exists for
hurry cargo- see the similar FIXME incmd/cargo.rs.Reference: PR #254 review comment from @elldritch
Suggested approach
Parse global flags first, then dispatch to the appropriate subcommand handler. This would allow acceleration to work correctly for commands like
cross --locked build.🤖 Generated with Claude Code