Closed jayvdb closed 11 months ago
Do you see any impact besides the unfortunate warning? It sounds as though there is a potential issue of one doc stomping on the other, although I haven't noticed that in practice.
Reading through the issue, it appears that there's fairly widespread acknowledgement that this is a bug cargo/rustdoc will need to fix. We don't actually need to document butane_cli
so I tried adding doc=false
to the bin target, but it doesn't seem to make a difference for the warning.
If you're not seeing concrete impact I'm going to close this as it's not clear that there's any reasonable fix at the project level.
The result locally is that 'butane' docs are the cli, not the lib, and as a result they are blank. I didnt look for workarounds yet.
Ah, ok, I'm not seeing that but it fits with the description in the linked bug of it being arbitrary which one wins.
For viewing docs locally if we don't find a workaround, I believe this should work reliably
cd butane && cargo +nightly doc --all-features --open
(or run make docview
which runs this)
yes, that works, and IMO is good enough.
Not sure what the options are to resolve this.
Running
> rustup run stable cargo doc
locally results in