-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help cargo to break dependency cycle caused by dev deps #3980
Conversation
Doesn't that possibly break some doc links? |
I don't see how it could break doc links. To have any undocumented types you'd have to use types from the dev dependency in a non-test build of the library, and that is not allowed and won't compile. |
75eb67f
to
1a093de
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah right, I thought doclinks would be able to resolve through dev deps, but apparently they aren't (so cargo doc does yield an unresolved link warning)
okfm then ¯\_(ツ)_/¯
(Not sure why CI is failing though)
The failing CI is caused by a regression in rustc. I've filled rust-lang/rust#123622 for that. |
Head branch was pushed to by a user without write access
Would it be possible to rebase this PR on top of the latest master version to pull in the fixes for the CI setup? (Sorry for that…) |
Thanks for submitting this PR ❤️ |
Help cargo to break dependency cycle caused by dev deps
This in fact has no impact on rustdoc according to diesel-rs/diesel#3980 (comment)
Cargo can automatically remove
path
dependencies when publishing when they don't have aversion
specified.This way it should be possible to publish crates without editing their
Cargo.toml
, and therefore keep their vcs metadata.