rust/compiler/rustc_const_eval/Cargo.toml, branch masterhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=master2025-09-02T09:12:54+00:00Revert introduction of `[workspace.dependencies]`.2025-09-02T09:12:54+00:00Nicholas Nethercoten.nethercote@gmail.com2025-09-02T09:09:13+00:00urn:sha1:301655eafe56a4b5064adebd412becf94b59221c
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.
Add `rustc_apfloat` to `[workspace.dependencies]`.2025-08-28T10:10:55+00:00Nicholas Nethercoten.nethercote@gmail.com2025-08-27T10:11:34+00:00urn:sha1:ce02d34b2faa2f4b43bb438bf4f7021d54e79c92Add `either` to `[workspace.dependencies]`.2025-08-28T10:10:55+00:00Nicholas Nethercoten.nethercote@gmail.com2025-08-27T10:03:15+00:00urn:sha1:d263d3a88ce2d339a16587fdb60d60a208ea4f6bAdd `tracing` to `[workspace.dependencies]`.2025-08-27T04:21:19+00:00Nicholas Nethercoten.nethercote@gmail.com2025-08-22T00:39:58+00:00urn:sha1:c50d2cc8078280a0dfdd562c7688e81b664e5880remove rustc_attr_data_structures2025-07-31T12:19:27+00:00Jana Dönszelmannjana@donsz.nl2025-07-31T09:00:40+00:00urn:sha1:e1d3ad89c7a2ad4f5d944a7fee1298ffe8c99645don't depend on rustc_attr_parsing if rustc_data_structures will do2025-05-09T21:16:55+00:00mejrs59372212+mejrs@users.noreply.github.com2025-05-09T21:16:55+00:00urn:sha1:684b7b70f4940a0abfecd3d95fe339960d6048d4Stop relying on rustc_type_ir in non-type-system crates2025-03-15T06:42:48+00:00Michael Gouletmichael@errs.io2025-03-13T18:05:00+00:00urn:sha1:b88f85a4106ca0a53a1dab6d605cf56a0cc945acRevert "Use workspace lints for crates in `compiler/` #138084"2025-03-10T10:12:47+00:00许杰友 Jieyou Xu (Joe)39484203+jieyouxu@users.noreply.github.com2025-03-10T10:12:34+00:00urn:sha1:063ef18fdc10cb0eb49e1af855e1a8e807e73eed
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.
Specify rust lints for `compiler/` crates via Cargo.2025-03-07T21:41:09+00:00Nicholas Nethercoten.nethercote@gmail.com2025-03-06T00:53:30+00:00urn:sha1:beba32cebb4fb2ef8f02c4fc898a9d31f1b03c61
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.
Upgrade the compiler to edition 20242025-02-22T00:01:48+00:00Michael Gouletmichael@errs.io2025-02-20T18:37:58+00:00urn:sha1:76d341fa09c423e601e2c47f8e4d165fcb7c21aa