-
Notifications
You must be signed in to change notification settings - Fork 660
☂️ Tracking issues or potential improvement we could make after upgrades to the Rust toolchain #3054
Comments
rustdoc::broken_intra_doc_links : #3053 (comment) |
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)) |
Done |
This issue is stale because it has been open 14 days with no activity. |
Someone already filed an issue for the false positive of |
This issue is stale because it has been open 14 days with no activity. |
This issue is stale because it has been open 14 days with no activity. |
Task
Issues after upgrade to 1.63.0
macro_export
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 (likeauthors
,repository
,licence
oredition
) to the rootCargo.toml
fileFrom 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)The text was updated successfully, but these errors were encountered: