Utilizing Display on a Path could suggest calling display()

[jrmuizel]

    let path = Path::new("/tmp/foo/bar.txt");
    println!("{}", path);

gives

  = note: `std::path::Path` cannot be formatted with the default formatter; try using `:?` instead if you are using a format string
  = note: required because of the requirements on the impl of `std::fmt::Display` for `&std::path::Path`
  = note: required by `std::fmt::Display::fmt`

It would be nice if rustc suggested calling display() on the path.

[GuillaumeGomez]

Well, no. println! is trying to call the Display trait. It's up to the user to check the docs in such cases. At least, for me there is nothing wrong here.

[jrmuizel]

The problem is that most people probably assume that paths are printable and are unaware that they require a lossy conversion to utf-8. Special casing some help to point users at the 'display()' method seems like a nice thing to do to compensate for having to explicitly call display() instead of just implementing Display on path directly.

[Mark-Simulacrum]

I feel like we should deprecate display in favor of to_string_lossy on Path, really. The only difference I think is that display() is lazy. However, this specific issue is something that seems decent to solve, so keeping it.