Argument doesn't conflict with subcommand even if it's set

[nix-enthusiast]

Clap version: 4.4.14
rustc version: 1.75.0
Code:

use clap::{Arg, ArgAction, Command};
use itertools::Itertools;
use std::process::exit;

fn main() {
    let matches = Command::new("cmd")
        .subcommand_precedence_over_arg(true)
        .args_conflicts_with_subcommands(true)
        .arg_required_else_help(true)
        .arg(
            Arg::new("foo")
                .short('f')
                .long("foo")
                .action(ArgAction::SetTrue)
                .exclusive(true)
        )
        .subcommand(
            Command::new("bar")
                .short_flag('B')
                .long_flag("bar")
                .arg_required_else_help(true)
                .arg(
                    Arg::new("baz")
                        .short('b')
                        .long("baz")
                        .action(ArgAction::Append)
                        .num_args(1..),
                ),
        );

    let a = matches.try_get_matches();

    match &a {
        Ok(ok) => {
            if ok.get_flag("foo") {
                println!("-f is used")
            };

            #[allow(clippy::disallowed_names)]
            if let Some(bar) = ok.subcommand_matches("bar") {
                if let Some(baz) = bar.get_many::<String>("baz")
                
                {if baz.len() % 2 != 0 {
                    println!("error");
                    exit(1)
                }

                for (first, second) in baz.tuples() {
                    println!("{} {}", first, second)
                }}
            }
        }
        Err(err) => {
            match err.kind() {
                clap::error::ErrorKind::UnknownArgument => println!("Unknown Argument"),
                clap::error::ErrorKind::ArgumentConflict => println!("Argument conflict"),
                clap::error::ErrorKind::DisplayHelpOnMissingArgumentOrSubcommand => {
                    println!("Subcommand needs an argument")
                }
                clap::error::ErrorKind::InvalidValue => println!("Argument needs a value"),
                clap::error::ErrorKind::DisplayHelp => {
                    println!("help");
                    exit(0)
                }
                clap::error::ErrorKind::InvalidSubcommand => println!("Invalid subcommand"),
                _ => println!("Unknown error"),
            }
            exit(1)
        }
    }
}

I used .subcommand_precedence_over_arg(true) and .args_conflicts_with_subcommands(true) but it doesn't work:

$ cargo run -- -f -Bb 1 2 3 4
    Finished dev [unoptimized + debuginfo] target(s) in 0.03s
     Running `target/debug/args -f -Bb 1 2 3 4`
-f is used
1 2
3 4
$

[epage]

This is a bug. Our handling of args_conflicts_with_subcommands is exclusive to subcommand names and not flags and we do this by checking if the flag if an arg doesn't exist (https://github.com/clap-rs/clap/blob/master/clap_builder/src/parser/parser.rs#L493) which means it likely is also broken with subcommand_precedence_over_arg

[nix-enthusiast]

I understand, It seems we will wait the next release.

[epage]

I would recommend creating issues if you want them fixed. We don't work out of Discussions for our backlog. While I try to get to more fundamental bugs like this more quickly, the surest way that fixes are in the next release is to contribute the fixes.

[nix-enthusiast]

Thanks, I will return this bug into issue tomorrow.