Skip to content
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.

☂️ Tracking issues or potential improvement we could make after upgrades to the Rust toolchain #3054

Closed
5 of 6 tasks
IWANABETHATGUY opened this issue Aug 12, 2022 · 8 comments
Labels
A-Tooling Area: our own build, development, and release tooling umbrella Issue to track a collection of other issues
Milestone

Comments

@IWANABETHATGUY
Copy link
Contributor

IWANABETHATGUY commented Aug 12, 2022

Task

Issues after upgrade to 1.63.0

  • rustdoc::broken_intra_doc_links can't detect the macro_export
  • let_and_return rule will cause a borrow checker issue.

Potential improvements we could make

  • From Rust 1.64: Cargo now supports inheriting some package attributes from the workspace (see https://doc.rust-lang.org/cargo/reference/workspaces.html#the-package-table for the list of supported attributes), we could move some of the attributes currently duplicated between all crates (like authors, repository, licence or edition) to the root Cargo.toml file
  • From Rust 1.63: With the standard library Mutex and RwLock being const-constructible it's now possible to use these in the DiffReport of the Prettier test suite
  • From Rust 1.62 it's now possible to derive the Default trait on enums, we could track down and remove the manual implementations for these
  • From Rust 1.61 the Termination trait and ExitCode type are now stable, meaning we could implement stable exit codes for the CLI (this could be done in the incoming refactor of diagnostics)
@IWANABETHATGUY IWANABETHATGUY added the umbrella Issue to track a collection of other issues label Aug 12, 2022
@IWANABETHATGUY
Copy link
Contributor Author

rustdoc::broken_intra_doc_links : #3053 (comment)
let_and_return : #3053 (comment)

@ematipico
Copy link
Contributor

Hi @IWANABETHATGUY , could you please update the description and explain what's this umbrella for?

@leops
Copy link
Contributor

leops commented Aug 12, 2022

Hi @IWANABETHATGUY , could you please update the description and explain what's this umbrella for?

I think we may "refactor" this umbrella to track both issues that are introduced in upgrades to the Rust toolchain (mostly Clippy false positives), and possible improvements to the existing codebase made possible by newly stabilized APIs (I came up with a short list of these here: #3053 (comment))

@IWANABETHATGUY IWANABETHATGUY changed the title ☂️ False positive clippy error introduced by 1.63.0 rust-toolchain ☂️ Tracking issues or potential improvement we could make after upgrade to 1.63.0 rust-toolchain Aug 13, 2022
@IWANABETHATGUY
Copy link
Contributor Author

Done

@github-actions
Copy link

github-actions bot commented Sep 7, 2022

This issue is stale because it has been open 14 days with no activity.

@ematipico
Copy link
Contributor

ematipico commented Sep 8, 2022

Someone already filed an issue for the false positive of let_and_return: rust-lang/rust-clippy#8114

@github-actions
Copy link

This issue is stale because it has been open 14 days with no activity.

@leops leops removed the S-Stale label Sep 23, 2022
@leops leops changed the title ☂️ Tracking issues or potential improvement we could make after upgrade to 1.63.0 rust-toolchain ☂️ Tracking issues or potential improvement we could make after upgrades to the Rust toolchain Sep 23, 2022
@ematipico ematipico added the A-Tooling Area: our own build, development, and release tooling label Sep 23, 2022
@ematipico ematipico added this to the 10.0.0 milestone Sep 23, 2022
@github-actions
Copy link

This issue is stale because it has been open 14 days with no activity.

@github-actions github-actions bot added S-Stale and removed S-Stale labels Oct 10, 2022
@ematipico ematipico moved this to Done in Rome 2022 Nov 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Tooling Area: our own build, development, and release tooling umbrella Issue to track a collection of other issues
Projects
Status: Done
Development

No branches or pull requests

3 participants