rust/compiler/rustc_codegen_ssa/src/assert_module_sources.rs, branch 1.82.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.82.02024-07-28T22:26:52+00:00Reformat `use` declarations.2024-07-28T22:26:52+00:00Nicholas Nethercoten.nethercote@gmail.com2024-07-28T22:13:50+00:00urn:sha1:84ac80f1921afc243d71fd0caaa4f2838c294102
The previous commit updated `rustfmt.toml` appropriately. This commit is
the outcome of running `x fmt --all` with the new formatting options.
Remove `#[macro_use] extern crate tracing` from `rustc_codegen_ssa`.2024-05-23T08:02:40+00:00Nicholas Nethercoten.nethercote@gmail.com2024-05-22T05:08:26+00:00urn:sha1:8ae0694fcb5887958580145f051bce852f4c8c50Rename `IntoDiagnosticArg` as `IntoDiagArg`.2024-03-10T22:12:19+00:00Nicholas Nethercoten.nethercote@gmail.com2024-03-05T05:53:24+00:00urn:sha1:a09b1d33a703d4ed412e70d3197e73ba7e0937f9
Also rename `into_diagnostic_arg` as `into_diag_arg`, and
`NotIntoDiagnosticArg` as `NotInotDiagArg`.
Rename all `ParseSess` variables/fields/lifetimes as `psess`.2024-03-04T21:11:45+00:00Nicholas Nethercoten.nethercote@gmail.com2024-03-04T05:31:49+00:00urn:sha1:80d2bdb6191609c8a3940a1a7959ac1ac16e8ed6
Existing names for values of this type are `sess`, `parse_sess`,
`parse_session`, and `ps`. `sess` is particularly annoying because
that's also used for `Session` values, which are often co-located, and
it can be difficult to know which type a value named `sess` refers to.
(That annoyance is the main motivation for this change.) `psess` is nice
and short, which is good for a name used this much.
The commit also renames some `parse_sess_created` values as
`psess_created`.
Rename `DiagnosticArg{,Map,Name,Value}` as `DiagArg{,Map,Name,Value}`.2024-02-27T21:55:37+00:00Nicholas Nethercoten.nethercote@gmail.com2024-02-23T03:37:48+00:00urn:sha1:8199632aa88c15f8e8cba942b9e6c38826b141ddclean up potential_query_instability with FxIndexMap and UnordMap2024-02-14T10:36:37+00:00yukangmoorekang@gmail.com2024-02-11T11:50:50+00:00urn:sha1:3f27e4b3ea35c87c1e8a6b9b8a3c7e122f6299deRollup merge of #120485 - chenyukang:yukang-add-query-instability-check, r=michaelwoerister2024-01-30T15:57:51+00:00Guillaume Gomezguillaume1.gomez@gmail.com2024-01-30T15:57:51+00:00urn:sha1:27bc49656462c48f3b98ac1d8ce2b06d446e5ad3
add missing potential_query_instability for keys and values in hashmap
From https://github.com/rust-lang/rust/pull/120435#discussion_r1468883787,
These API are also returning iterator, so we need add `potential_query_instability` for them?
Remove the lifetime from `DiagnosticArgValue`.2024-01-30T07:46:06+00:00Nicholas Nethercoten.nethercote@gmail.com2024-01-30T04:27:16+00:00urn:sha1:5350edb9e8f4e194a2cad9a41b81d97a8ed52fab
Because it's almost always static.
This makes `impl IntoDiagnosticArg for DiagnosticArgValue` trivial,
which is nice.
There are a few diagnostics constructed in
`compiler/rustc_mir_build/src/check_unsafety.rs` and
`compiler/rustc_mir_transform/src/errors.rs` that now need symbols
converted to `String` with `to_string` instead of `&str` with `as_str`,
but that' no big deal, and worth it for the simplifications elsewhere.
add missing potential_query_instability for keys and values in hashmap2024-01-30T04:43:10+00:00yukangmoorekang@gmail.com2024-01-30T04:42:29+00:00urn:sha1:ad526d831e295facc198610a27350076aa5aa438rustc_codegen_ssa: Enforce `rustc::potential_query_instability` lint2024-01-13T15:05:53+00:00Jakub Beránekberykubik@gmail.com2023-12-29T12:41:35+00:00urn:sha1:4612edc53f998994cffaa1b5856d624ad3910c18