about summary refs log tree commit diff
path: root/compiler/rustc_pattern_analysis/Cargo.toml
AgeCommit message (Collapse)AuthorLines
2025-09-02Revert introduction of `[workspace.dependencies]`.Nicholas Nethercote-3/+3
This was done in #145740 and #145947. It is causing problems for people using r-a on anything that uses the rustc-dev rustup package, e.g. Miri, clippy. This repository has lots of submodules and subtrees and various different projects are carved out of pieces of it. It seems like `[workspace.dependencies]` will just be more trouble than it's worth.
2025-08-28Add `rustc-hash` to `[workspace.dependencies]`.Nicholas Nethercote-1/+1
2025-08-28Add `rustc_apfloat` to `[workspace.dependencies]`.Nicholas Nethercote-1/+1
2025-08-27Add `tracing` to `[workspace.dependencies]`.Nicholas Nethercote-1/+1
2025-07-31Tidy up `Cargo.toml` files.Nicholas Nethercote-1/+4
- Add some missing `tidy-alphabetical-*` markers. - Remove some unnecessary blank lines.
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
2024-11-03compiler: Remove unused rustc_target from Cargo.tomlsJubilee Young-2/+0
2024-10-27compiler: Add rustc_abi dependence to the compilerJubilee Young-0/+3
Depend on rustc_abi in compiler crates that use it indirectly but have not yet taken on that dependency, and are not entangled in my other PRs. This leaves an "excise rustc_target" step after the dust settles.
2024-10-20Update rustc-hash to version 2Noratrieb-1/+1
This brings in the new algorithm.
2024-03-30bump tracing-tree to 0.3klensy-1/+1
Only change is https://github.com/davidbarsky/tracing-tree/pull/76 dedupes tracing-log dupes nu-ansi-term
2024-03-19Add a crate-custom test harnessNadrieril-0/+4
2024-01-27Stop using derivative in rustc_pattern_analysisLaurențiu Nicola-1/+0
2024-01-17Don't rely on contiguous `VariantId`s outside of rustcNadrieril-0/+1
2024-01-12rustc_pattern_analysis no longer needs to be passed an arenaNadrieril-6/+0
2023-12-23Use `derivative` for better derive boundsNadrieril-0/+1
2023-12-15Make the crate compile on stableNadrieril-3/+12
2023-12-15Make the `rustc_data_structures` dependency optionalNadrieril-1/+2
2023-12-15Gate rustc-specific code under a featureNadrieril-8/+21
2023-12-11Extract exhaustiveness into its own crateNadrieril-0/+22