cargo-zigbuild test doesn't pass arguments through properly about cargo-zigbuild HOT 2 CLOSED

When testing of the other, similar cargo-zigbuild subcommands ("clippy", "run", and "rustc") I see that they don't provide a way to us a single -- argument to pass options to the underlying cargo subcommand. Instead, they parse the arguments, re-add the appropriate ones, then inject the -- separator between those subcommand arguments and any, unknown others that are intended for the underlying command (eg: rustc, clippy, or the newly-compiled binary).

cargo-zigbuild test just seems to be behaving differently than those others.

from cargo-zigbuild.

I believe messense/cargo-options#12 fixes (and explains the root cause of) the issue.

from cargo-zigbuild.