about summary refs log tree commit diff
AgeCommit message (Collapse)AuthorLines
2023-10-21Reword TO application comments.Camille GILLOT-3/+4
2023-10-21Simplify static if handling.Camille GILLOT-4/+6
2023-10-21Explicit notation.Camille GILLOT-0/+4
2023-10-21Rebase fallout.Camille GILLOT-25/+1
2023-10-21Document Condition.Camille GILLOT-0/+2
2023-10-21Make polarity an enum.Camille GILLOT-11/+23
2023-10-21Document mutated_statement.Camille GILLOT-4/+15
2023-10-21Improve naming and comments.Camille GILLOT-18/+46
2023-10-21Handle more terminators.Camille GILLOT-27/+95
2023-10-21Do not thread through loop headers.Camille GILLOT-35/+48
2023-10-21Implement JumpThreading pass.Camille GILLOT-18/+2375
2023-10-21Make instance an option in CostChecker.Camille GILLOT-10/+15
2023-10-21Extract cost checker from inliner.Camille GILLOT-88/+98
2023-10-20Auto merge of #116958 - oli-obk:coro, r=pnkfelixbors-3916/+3935
rename Generator to Coroutine implements https://github.com/rust-lang/compiler-team/issues/682 While I did an automated replacement, I went through all changes manually to avoid renaming things like "id generators", "code generator", ... I renamed files where that was necessary due to the contents referring to the crate name itself (mir opt, codegen or debuginfo tests), or required by tidy (feature gate docs) * [x] rename various remaining abbreviated references to generators. * [x] rename files * [x] rename folders * [x] add renamed feature: `generators`, ... r? `@ghost`
2023-10-20Replace all uses of `generator` in markdown documentation with `coroutine`Oli Scherer-52/+52
2023-10-20bless miriOli Scherer-8/+8
2023-10-20bless ui-fulldepsOli Scherer-2/+2
2023-10-20Bless coverage mapOli Scherer-3/+3
2023-10-20Fix stage0 core testsOli Scherer-3/+8
2023-10-20Rename `generator` folderOli Scherer-0/+0
2023-10-20Rename lots of files that had `generator` in their nameOli Scherer-81/+81
2023-10-20Re-add `generators` as a removed feature and point to the new feature nameOli Scherer-0/+6
2023-10-20Rename `Gen` to `Coro` in testsOli Scherer-12/+12
2023-10-20Rename `CoroutineKind::Gen` to `::Coroutine`Oli Scherer-25/+29
2023-10-20s/generator/coroutine/Oli Scherer-2197/+2201
2023-10-20s/Generator/Coroutine/Oli Scherer-1271/+1271
2023-10-20Auto merge of #116951 - compiler-errors:ir-file-structure, r=jackh726bors-1532/+1560
Restructure `rustc_type_ir` a bit 1. Split `sty` into new `ty_kind`/`region_kind`/`const_kind` modules, so that when we uplift more kinds (e.g. `PredicateKind`, `ClauseKind`, and `ExistentialPredicate`), they can live in their own simple-to-understand files. 2. Split up the `structural_impls` module, which is a kitchen sink of random impls -- move `TypeFoldable` and `TypeVisitable` impls into existing `fold` and `visit` modules, respectively. 3. Move the `DebugWithInfcx` trait and blanket impls into a new `debug` module, and `TypeFlags` definition into a new `flags` module. 5. Move `Interner` trait into a new `interner` module. I expect this file to get a lot larger as we make the interner more powerful for the trait solver refactor. r? `@ghost` for now, will assign once #116946 lands
2023-10-20Move some files aroundMichael Goulet-1520/+1548
2023-10-20Adjust importsMichael Goulet-12/+12
2023-10-20Auto merge of #116966 - clarfonthey:atomic-docs-typo, r=workingjubileebors-1/+1
Fix typo in atomic docs Maybe rustdoc or tidy should lint hanging backticks like this.
2023-10-20Auto merge of #116965 - estebank:issue-65329, r=cjgillotbors-37/+85
Move where doc comment meant as comment check The new place makes more sense and covers more cases beyond individual statements. ``` error: expected one of `.`, `;`, `?`, `else`, or an operator, found doc comment `//!foo --> $DIR/doc-comment-in-stmt.rs:25:22 | LL | let y = x.max(1) //!foo | ^^^^^^ expected one of `.`, `;`, `?`, `else`, or an operator | help: add a space before `!` to write a regular comment | LL | let y = x.max(1) // !foo | + ``` Fix #65329.
2023-10-20Auto merge of #116962 - estebank:issue-63835, r=oli-obkbors-1/+8
Do not bold main message in `--error-format=short` Fix #63835. Before: <img width="484" alt="Screenshot 2023-10-19 at 3 52 53 PM" src="https://github.com/rust-lang/rust/assets/1606434/9bd6cbd5-a4ce-4cc3-8c5f-60a8d3ad38da"> After: <img width="492" alt="Screenshot 2023-10-19 at 3 52 32 PM" src="https://github.com/rust-lang/rust/assets/1606434/0cf2417a-08f2-4074-860c-a88a838a4209">
2023-10-20Auto merge of #116946 - compiler-errors:movability-and-mutability, r=lcnrbors-88/+79
Uplift movability and mutability, the simple way Just make type_ir a dependency of ast. This can be relaxed later if we want to make the dependency less heavy. Part of rust-lang/types-team#124. r? `@lcnr` or `@jackh726`
2023-10-20Auto merge of #116899 - compiler-errors:closure-sig-infer, r=lcnrbors-0/+36
Add a test showing failing closure signature inference in new solver Been thinking a bit about how to make this test pass... but we don't actually have any good tests exercising this behavior in the suite. r? lcnr
2023-10-20Fix typo in atomic docsltdk-1/+1
2023-10-20Auto merge of #116785 - nnethercote:spec-Bytes-read, r=the8472bors-15/+60
Specialize `Bytes<R>::next` when `R` is a `BufReader`. This reduces the runtime for a simple program using `Bytes::next` to iterate through a file from 220ms to 70ms on my Linux box. r? `@the8472`
2023-10-20Move where doc comment meant as comment checkEsteban Küber-37/+85
The new place makes more sense and covers more cases beyond individual statements. ``` error: expected one of `.`, `;`, `?`, `else`, or an operator, found doc comment `//!foo --> $DIR/doc-comment-in-stmt.rs:25:22 | LL | let y = x.max(1) //!foo | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected one of `.`, `;`, `?`, `else`, or an operator | help: add a space before `!` to write a regular comment | LL | let y = x.max(1) // !foo | + ``` Fix #65329.
2023-10-20Auto merge of #116838 - gurry:116836-dup-macro-invoc-diag, r=petrochenkovbors-46/+13
Fix duplicate labels emitted in `render_multispan_macro_backtrace()` This PR replaces the `Vec` used to store labels with an `FxIndexSet` in order to eliminate duplicates Fixes #116836
2023-10-20Auto merge of #116875 - nnethercote:rustc_monomorphize, r=wesleywiserbors-54/+12
`rustc_monomorphize` cleanups Just some small improvements I found while looking over this code. r? `@wesleywiser`
2023-10-19Do not bold main message in `--error-format=short`Esteban Küber-1/+8
Fix #63835.
2023-10-20Specialize `Bytes<R>::next` when `R` is a `BufReader`.Nicholas Nethercote-15/+60
This reduces the runtime for a simple program using `Bytes::next` to iterate through a file from 220ms to 70ms on my Linux box.
2023-10-19Auto merge of #116874 - compiler-errors:elaborator-nits, r=wesleywiserbors-42/+39
Some small elaborator nits Didn't want to fold these into a totally unrelated pr.
2023-10-19Auto merge of #115214 - Urgau:rfc-3127-trim-paths, r=compiler-errorsbors-94/+582
Implement rustc part of RFC 3127 trim-paths This PR implements (or at least tries to) [RFC 3127 trim-paths](https://github.com/rust-lang/rust/issues/111540), the rustc part. That is `-Zremap-path-scope` with all of it's components/scopes. `@rustbot` label: +F-trim-paths
2023-10-19Auto merge of #116810 - cjgillot:mir-opt-check, r=oli-obkbors-589/+1444
Add FileCheck annotations to mir-opt tests. This PR makes compiletest run LLVM `FileCheck` tool on mir-opt tests. The check is *run by default*, except if disabled using `// skip-filecheck` comment. This ensures that we do not have a silently broken test. For now, the check is only run on the output of `--emit=mir`, ie. on PreCodegen MIR. I give an example on `reference_prop.rs`. r? `@oli-obk` cc `@RalfJung` Fixes https://github.com/rust-lang/rust/issues/85180
2023-10-19Uplift movability and mutability, the simple wayMichael Goulet-88/+79
2023-10-19FileCheck transmute.Camille GILLOT-2/+44
2023-10-19FileCheck inline_shims.Camille GILLOT-1/+4
2023-10-19FileCheck issue_106141.Camille GILLOT-1/+6
2023-10-19Mention skip in README.Camille GILLOT-0/+2
2023-10-19FileCheck lower_slice_len.Camille GILLOT-2/+3
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-25 17:27:22 +0000