about summary refs log tree commit diff
path: root/compiler/rustc_span/Cargo.toml
AgeCommit message (Collapse)AuthorLines
2025-03-10Revert "Use workspace lints for crates in `compiler/` #138084"许杰友 Jieyou Xu (Joe)-3/+0
Revert <https://github.com/rust-lang/rust/pull/138084> to buy time to consider options that avoids breaking downstream usages of cargo on distributed `rustc-src` artifacts, where such cargo invocations fail due to inability to inherit `lints` from workspace root manifest's `workspace.lints` (this is only valid for the source rust-lang/rust workspace, but not really the distributed `rustc-src` artifacts). This breakage was reported in <https://github.com/rust-lang/rust/issues/138304>. This reverts commit 48caf81484b50dca5a5cebb614899a3df81ca898, reversing changes made to c6662879b27f5161e95f39395e3c9513a7b97028.
2025-03-08Specify rust lints for `compiler/` crates via Cargo.Nicholas Nethercote-0/+3
By naming them in `[workspace.lints.rust]` in the top-level `Cargo.toml`, and then making all `compiler/` crates inherit them with `[lints] workspace = true`. (I omitted `rustc_codegen_{cranelift,gcc}`, because they're a bit different.) The advantages of this over the current approach: - It uses a standard Cargo feature, rather than special handling in bootstrap. So, easier to understand, and less likely to get accidentally broken in the future. - It works for proc macro crates. It's a shame it doesn't work for rustc-specific lints, as the comments explain.
2025-02-22Upgrade the compiler to edition 2024Michael Goulet-1/+1
2025-02-16Move hashes from rustc_data_structure to rustc_hashes so they can be shared ↵Ben Kimock-0/+1
with rust-analyzer
2024-10-12Update unicode-width to 0.2.0printfn-1/+1
2024-10-01add unstable support for outputting file checksums for use in cargoJacob Kiesel-0/+1
2024-07-12rustc_span: derivative -> derive-wherePavel Grigorenko-1/+1
2024-04-19Stop sorting `Span`s' `SyntaxContext`, as that is incompatible with incrementalOli Scherer-0/+1
2024-03-06Optimize Symbol::integer by utilizing itoa in-place formattingUrgau-0/+1
2023-10-30Clean up `rustc_*/Cargo.toml`.Nicholas Nethercote-9/+9
- Sort dependencies and features sections. - Add `tidy` markers to the sorted sections so they stay sorted. - Remove empty `[lib`] sections. - Remove "See more keys..." comments. Excluded files: - rustc_codegen_{cranelift,gcc}, because they're external. - rustc_lexer, because it has external use. - stable_mir, because it has external use.
2023-10-19Initiate the inner usage of `cfg_match`Caio-1/+0
2023-07-03Upgrade to indexmap 2.0.0Josh Stone-1/+1
The new version was already added to the tree as an indirect dependency in #113046, but now our direct dependents are using it too.
2023-03-25Update indexmap and rayon cratesJohn Kåre Alsaker-1/+1
2023-03-21Eagerly intern and check CrateNum/StableCrateId collisionsOli Scherer-0/+1
2023-01-10Remove duplicate sha-1 dependencyEric Huss-1/+1
2022-12-20Bump `cfg-if` to `1.0`Chris Denton-1/+1
2022-09-29Remove from compiler/ cratesreez12g-1/+0
2022-02-13Update `sha1`, `sha2`, and `md5` dependenciespierwill-3/+3
This removes the `cpuid-bool` dependency, which is deprecated, while adding `crypto-common` as a new dependency.
2021-09-20Migrate to 2021Mark Rousskov-1/+1
2021-07-29rfc3052: Remove authors field from Cargo manifestsJade-1/+0
Since RFC 3052 soft deprecated the authors field anyway, hiding it from crates.io, docs.rs, and making Cargo not add it by default, and it is not generally up to date/useful information, we should remove it from crates in this repo.
2021-06-24rustc_span: Explicitly handle crates that differ from package namesJosh Triplett-2/+2
The sha-1 and md-5 packages contain crates named sha1 and md5, respectively. This discrepancy makes it somewhat more challenging to automate detection of unused crates. Explicitly rename the packages to the names of the crates they contain, to simplify such detection.
2020-10-14Add support for SHA256 source file hashing for LLVM 11+.Arlo Siemsen-2/+3
2020-08-30mv compiler to compiler/mark-0/+21