about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2025-07-10Fix `--skip-std-check-if-no-download-rustc`Jakub Beránek-7/+31
Since https://github.com/rust-lang/rust/pull/143048, we now explicitly set the build compiler for `check::Std`, which caused it to be built before we checked `--skip-std-check-if-no-download-rustc`. So I moved the check earlier to `make_run`, which resolves it. I also added a regression test for this. Sadly we can't really test for the positive case easily (when download-ci-rustc is enabled), but we can test the negative cases, where it is disabled.
2025-07-10Only provide `is_windows_msvc` to gate on windows-msvcJieyou Xu-34/+29
And not both `is_windows_msvc` and `is_msvc`.
2025-07-10remove unnecessary parens in rust-analyzeryukang-1/+1
2025-07-10Revert "remove `if-let` chains"Laurențiu Nicola-7/+6
This reverts commit fcc81a38b3ed55447735f71e8d374fcb36c22f24.
2025-07-10fmtThe Miri Cronjob Bot-1/+3
2025-07-10Merge from rustcThe Miri Cronjob Bot-854/+3420
2025-07-10Preparing for merge from rustcThe Miri Cronjob Bot-1/+1
2025-07-10Merge pull request #20212 from ChayimFriedman2/dyn-hintShoyu Vanilla (Flint)-5/+31
fix: Fixes for `dyn` inlay hint
2025-07-10Migrate `convert_match_to_let_else` assist to use `SyntaxEditor`Hayashi Mikihiro-13/+15
Signed-off-by: Hayashi Mikihiro <34ttrweoewiwe28@gmail.com>
2025-07-10Put the expression stuff in the expression store behind an `Option<Box>`Chayim Refael Friedman-271/+419
And leave only the type stuff without it. This is because most expression stores don't have anything but types (e.g. generics, fields, signatures) so this saves a lot of memory. This saves 58mb on `analysis-stats .`.
2025-07-10Remove uncessary parens in closure body with unused lintyukang-5/+11
2025-07-09feat(lexer): Allow including frontmatter with 'tokenize'Ed Page-26/+25
2025-07-09do not invent a nameTshepang Mbambo-1/+1
Nowhere else is this called "Dist check"
2025-07-09distcheck had only one possible invocationTshepang Mbambo-1/+3
That is, calling it an example is misleading
2025-07-09add missing wordTshepang Mbambo-1/+1
2025-07-09Update LLVM submoduleDaniel Paoliello-0/+0
2025-07-09Make `AsmExpr` have `AstId`Chayim Refael Friedman-10/+29
We need it because `global_asm!()` is an item. It's unfortunate that such thing can slip in and I see no way to automatically catch that, but thankfully analysis-stats on self has caught that.
2025-07-09Merge pull request #20214 from rust-lang/update-msrvChayim Refael Friedman-1/+1
Update MSRV to 1.88.0
2025-07-09Update MSRV to 1.88.0Chayim Refael Friedman-1/+1
2025-07-09miri: fix out-of-bounds error for ptrs with negative offsetsRalf Jung-0/+53
2025-07-09Put `dyn` inlay hints in their correct place in presence of parenthesesChayim Refael Friedman-3/+14
2025-07-09Disable the `diagnostics_dont_block_typing` test on CIChayim Refael Friedman-1/+2
It's failing to much. We need to fix it, but my changes are unlikely to be the cause.
2025-07-09Don't show `dyn` hint in a HRTB boundChayim Refael Friedman-2/+17
2025-07-10migrate `convert_named_struct_to_tuple_struct` assist to use 'SyntaxEditor'Hayashi Mikihiro-6/+9
Signed-off-by: Hayashi Mikihiro <34ttrweoewiwe28@gmail.com>
2025-07-09Make `global_asm!()` workChayim Refael Friedman-36/+58
Because apparently, we were not accepting inline asm in item position, completely breaking it.
2025-07-09Merge pull request #20109 from Hmikihiro/generate_new_tuple_fieldShoyu Vanilla (Flint)-24/+385
feat: Generate `new` for tuple struct
2025-07-09Differentiate between `asm!()`, `global_asm!()` and `naked_asm!()`, and make ↵Chayim Refael Friedman-16/+198
only `asm!()` unsafe
2025-07-09Don't hash the `SyntaxKind` in the ast idChayim Refael Friedman-41/+36
There is no need to, it's already stored in the `kind`.
2025-07-09bootstrap/miri: avoid rebuilds for test buildsRalf Jung-2/+8
2025-07-09Massage `lib.rs` so it can be rustfmt'dJieyou Xu-66/+42
Even if the formatting isn't strictly "better", it at least allows rustfmtting it automatically.
2025-07-09Sort and document `run-make-support` dependenciesJieyou Xu-4/+13
2025-07-09Bump `run-make-support` to Edition 2024Jieyou Xu-1/+1
2025-07-09Don't attempt to version `run-make-support`Jieyou Xu-1/+1
Purely internal test support library.
2025-07-09Remove `run-make-support` CHANGELOGJieyou Xu-83/+0
Hopelessly outdated, and this support library is purely internal.
2025-07-09Make `LlvmBitcodeLinker` a `ToolTarget` toolJakub Beránek-37/+49
2025-07-09Extend dist extended tools testJakub Beránek-5/+14
2025-07-09Make `LldWrapper` a `ToolTarget` toolJakub Beránek-50/+78
2025-07-09Make `WasmComponentLd` a `ToolTarget` toolJakub Beránek-16/+111
2025-07-09Port `RemoteTestServer` to `ToolTarget`Jakub Beránek-16/+21
2025-07-09Add `Mode::ToolTarget`Jakub Beránek-39/+104
2025-07-09Rename `compiler` to `build_compiler`Jakub Beránek-30/+31
2025-07-09Auto merge of #143472 - dianne:deref-pat-column-check, r=Nadrierilbors-0/+8
`rustc_pattern_analysis`: always check that deref patterns don't match on the same place as normal constructors In rust-lang/rust#140106, deref pattern validation was tied to the `deref_patterns` feature to temporarily avoid affecting perf. However: - As of rust-lang/rust#143414, box patterns are represented as deref patterns in `rustc_pattern_analysis`. Since they can be used by enabling `box_patterns` instead of `deref_patterns`, it was possible for them to skip validation, resulting in an ICE. This fixes that and adds a regression test. - External tooling (e.g. rust-analyzer) will also need to validate matches containing deref patterns, which was not possible. This fixes that by making `compute_match_usefulness` validate deref patterns by default. In order to avoid doing an extra pass for anything with patterns, the second commit makes `RustcPatCtxt` keep track of whether it encounters a deref pattern, so that it only does the check if so. This is purely for performance. If the perf impact of the first commit is negligible and the complexity cost introduced by the second commit is significant, it may be worth dropping the latter. r? `@Nadrieril`
2025-07-09various native-lib-trace-related fixupsNia Espera-338/+312
Co-Authored-By: Ralf Jung <post@ralfj.de>
2025-07-09Add doc cross-compilation testJakub Beránek-0/+16
2025-07-09Add `doc library` test for a no_std targetJakub Beránek-1/+17
2025-07-09Add a new maintainer to the wasm32-wasip1 targetMarcin Kolny-0/+1
2025-07-09tweak some git clone commandsTshepang Mbambo-6/+6
- --depth=1 is more useful for once-off uses, like on ci - .git postfix on github repo url is not needed
2025-07-09use a consistent (and recommended) invocationTshepang Mbambo-7/+7
./x is recommended over running ./x.py directly, and is the more commonly-used invocation of bootstrap in the guide
2025-07-08Rollup merge of #143606 - lambdageek:configure-write-last-key, r=KobzolTrevor Gross-8/+18
configure.py: Write last key in each section The loop that writes the keys in each section of bootstrap.toml accumulates all the commented lines before a given key and emits them when it reaches the next key in the section. This ends up dropping lines accumulated for the last key Fixes rust-lang/rust#143605
2025-07-08Rollup merge of #143520 - Stypox:enter_trace_span-closure, r=RalfJungTrevor Gross-2/+10
Fix perf regression caused by tracing See rust-lang/rust#143334, this is another alternative that may be worth benchmarking as suggested in https://github.com/rust-lang/rust/pull/143334#issuecomment-3038953172. r? ``@RalfJung``
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 19:19:26 +0000