`cargo doc` produces seemingly invalid suggestions to run `cargo fix`

[waywardmonkeys]

I was building documentation for the parry set of libraries and got this notification at the end:

warning: `parry2d` (lib doc) generated 12 warnings (run `cargo fix --lib -p parry2d` to apply 4 suggestions)
warning: `parry2d-f64` (lib doc) generated 12 warnings (run `cargo fix --lib -p parry2d-f64` to apply 4 suggestions)
warning: `parry3d` (lib doc) generated 9 warnings (run `cargo fix --lib -p parry3d` to apply 1 suggestion)
warning: `parry3d-f64` (lib doc) generated 9 warnings (run `cargo fix --lib -p parry3d-f64` to apply 1 suggestion)

The warnings were for things like this:

warning: this URL is not a hyperlink
 --> crates\parry2d\../../src\transformation\ear_clipping.rs:2:14
  |
2 | //! Based on https://github.com/ivanfratric/polypartition, contributed by embotech AG.
  |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use an automatic link instead: `<https://github.com/ivanfratric/polypartition>`
  |
  = note: bare URLs are not automatically turned into clickable links

Unfortunately, running any of those commands doesn't appear to apply those fixes.

Meta

This happens with both the current stable and a recently nightly:

>cargo +nightly --verbose --version
cargo 1.72.0-nightly (b0fa79679 2023-06-03)
release: 1.72.0-nightly
commit-hash: b0fa79679e717cd077b7fc0fa4166f47107f1ba9
commit-date: 2023-06-03
host: x86_64-pc-windows-msvc
libgit2: 1.6.4 (sys:0.17.1 vendored)
libcurl: 8.1.2-DEV (sys:0.4.63+curl-8.1.2 vendored ssl:Schannel)
os: Windows 10.0.22621 (Windows 11 Professional) [64-bit]

>cargo --verbose --version
cargo 1.70.0 (ec8a8a0ca 2023-04-25)
release: 1.70.0
commit-hash: ec8a8a0cabb0e0cadef58902470f6c7ee7868bdc
commit-date: 2023-04-25
host: x86_64-pc-windows-msvc
libgit2: 1.6.3 (sys:0.17.0 vendored)
libcurl: 8.0.1-DEV (sys:0.4.61+curl-8.0.1 vendored ssl:Schannel)
os: Windows 10.0.22621 (Windows 10 Pro) [64-bit]

[ehuss]

Thanks for the report! Transferred to rust-lang/cargo, as this is a cargo issue.

cargo fix is currently not capable of applying fixes from rustdoc. Either it needs to gain that ability, or it should not suggest running cargo fix when running rustdoc.