Can a PathBuf argument have a PathBuf default_value_t option?

[iampi31415]

• Is it possible to use default_value_t=PathBuf::from(FILEPATH) ?

For example

// Defaults
const FILEPATH: &str = "./urls";

#[derive(Parser, Debug)]
#[command(version, about, long_about = None)]
struct Args {
    #[arg(
        group = "input",
        // See error after snippet.
        default_value_t = PathBuf::from(FILEPATH),
    )]
    path: PathBuf,
}

The rust-analyzer error is:

   The trait bound `PathBuf: ToString` is not satisfied
   required for `PathBuf` to implement `ToString`

So I suspect that this is implying that the default value needs to be String (because it is asking for the trait for conversion?)

Then it would mean that one can only use primitive types assigned to the default?
In that case I will need no default and later on use unwrap_or but I am just checking that this is correct, or maybe get any suggestion.

[epage]

Then it would mean that one can only use primitive types assigned to the default?

Anything that implements Display can use default_value_t. We insert defaults very early in the parsing process when everything is an OsString and so we need some way to convert the typed value to an OsString and Display / ToString is the most universal way to do so.

[iampi31415]

So the answer is that it can not have a PathBuf because Display is not implemented, and I can not implement 3rd party traits on 3rd party Structs. Is this correct or am I misreading your response ?

[epage]

That is correct