rust/compiler/rustc_log/Cargo.toml, branch perf-tmphttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp2025-09-08T16:23:37+00:00Update tracing, again2025-09-08T16:23:37+00:00Daniel Paoliellodanpao@microsoft.com2025-09-04T00:12:03+00:00urn:sha1:266f8c9c0073745044a8eaeef5803b90090f5ad5unpin tracing_core2025-09-04T10:24:42+00:00klensyklensy@users.noreply.github.com2024-07-04T11:43:27+00:00urn:sha1:17b27d8e6c7ecce909d3b0bd072378c7a0854d78Revert 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 `tracing` to `[workspace.dependencies]`.2025-08-27T04:21:19+00:00Nicholas Nethercoten.nethercote@gmail.com2025-08-22T00:39:58+00:00urn:sha1:c50d2cc8078280a0dfdd562c7688e81b664e5880Use `-Wunused_crate_dependencies` for compiler crates.2025-03-19T21:59:43+00:00Nicholas Nethercoten.nethercote@gmail.com2025-03-03T07:59:30+00:00urn:sha1:8121958fda43759fa94e3f74f7cdbb595ddcc0e5
It's very useful. There are some false positives involving integration
tests in `rustc_pattern_analysis` and `rustc_serialize`. There is also a
false positive involving `rustc_driver_impl`'s
`rustc_randomized_layouts` feature. And I removed a `rustc_span` mention
in a doc comment in `rustc_log` because it wasn't integral to the
comment but caused a dev-dependency.
Revert "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:76d341fa09c423e601e2c47f8e4d165fcb7c21aaBump tracing-tree and allow rendering lines again2024-06-12T10:11:41+00:00Oli Scherergit-spam-no-reply9815368754983@oli-obk.de2024-06-11T08:55:48+00:00urn:sha1:185a48d4b266722d550474a620c0e37e28b1c6d6bump tracing-tree to 0.32024-03-30T14:39:43+00:00klensyklensy@users.noreply.github.com2024-03-30T14:39:43+00:00urn:sha1:71ea506d3df77b77a38b6f1ad0c7926c08b37f32
Only change is https://github.com/davidbarsky/tracing-tree/pull/76
dedupes tracing-log
dupes nu-ansi-term