Skip to content
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

Fix lint warnings: "lint intra_doc_link_resolution_failure has been renamed to broken_intra_doc_links" #279

Closed
daira opened this issue Aug 22, 2020 · 5 comments

Comments

@daira
Copy link
Contributor

daira commented Aug 22, 2020

GitHub Actions / Nightly lint

ff/src/lib.rs#L5 and group/src/lib.rs#L2 :

lint `intra_doc_link_resolution_failure` has been renamed to `broken_intra_doc_links`
@daira daira changed the title Fix lint warnings in ff and group: "lint intra_doc_link_resolution_failure has been renamed to broken_intra_doc_links" Fix lint warnings: "lint intra_doc_link_resolution_failure has been renamed to broken_intra_doc_links" Aug 22, 2020
@str4d
Copy link
Contributor

str4d commented Aug 22, 2020

In the interim, we can pin a version of nightly before this change was made, if we want to avoid the lint warnings in other PRs.

@daira
Copy link
Contributor Author

daira commented Aug 22, 2020

Well, that would mean that if any other warnings are added then we wouldn't see them. I think it's fine to just ignore these warnings for now. (I'm surprised that this is a warning at all before the broken_intra_doc_links replacement is in stable, tbh. Aren't you supposed to add something to stable and then deprecate the old thing?)

@str4d
Copy link
Contributor

str4d commented Sep 19, 2020

Apparently this is expected in the lint renaming process: rust-lang/rust#74926 (comment)

The standard fix would be to apply allow(unknown_lints) until rust-lang/rust#74430 is merged and we are on a stable release containing the stabilised lint.

@str4d
Copy link
Contributor

str4d commented Dec 17, 2020

We can rename the lints once our MSRV is 1.48.0.

@daira
Copy link
Contributor Author

daira commented Feb 6, 2021

Rust 1.48.0 is nearly 3 months old; why not update the MSRV now? Those warnings really get in my way when reviewing.

@str4d str4d closed this as completed in 9d9c057 Mar 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants