about summary refs log tree commit diff
AgeCommit message (Collapse)AuthorLines
2023-11-16Address PR commentsCelina G. Val-4/+3
2023-11-16Add more APIs and fix `Instance::body`Celina G. Val-47/+422
Add more APIs to retrieve information about types, and add more instance resolution options. Make `Instance::body()` return an Option<Body>, since not every instance might have an available body. For example, foreign instances, virtual instances, dependencies.
2023-11-16Auto merge of #15913 - lnicola:bump-libc, r=lnicolabors-4/+5
internal: Bump libc CC https://github.com/rust-lang/rust/pull/117981
2023-11-16Bump libcLaurențiu Nicola-4/+5
2023-11-16Auto merge of #116097 - jackh726:higher-ranked-lifetime-error-backup, ↵bors-13/+80
r=compiler-errors Try to use approximate placeholder regions when outputting an AscribeUserType error in borrowck Fixes #114866 Hi from GOSIM :)
2023-11-16Fix bug on MIRVisitorCelina G. Val-2/+2
We were not iterating over all local variables due to a typo.
2023-11-16Add more SMIR internal impl and callback return valueCelina G. Val-21/+159
In cases like Kani, we will invoke the rustc_internal run command directly for now. It would be handly to be able to have a callback that can return a value. We also need extra methods to convert stable constructs into internal ones, so we can break down the transition into finer grain commits.
2023-11-16bootstrap: only show PGO warnings when verboseJosh Stone-1/+3
Building rustc with `--rust-profile-use` is currently dumping a lot of warnings of "no profile data available for function" from `rustc_smir` and `stable_mir`. These simply aren't exercised by the current profile- gathering steps, but that's to be expected for new or experimental functionality. I think for most people, these warnings will be just noise, so it makes sense to only have them in verbose builds.
2023-11-16Update rust-cache GHA in deploy workflowPhilipp Krones-1/+3
This action was way outdated, produced a lot of warnings and didn't seem to work anymore.
2023-11-16fix: Update CONTRIBUTING.md recommend -> recommendedZephyr-1/+1
2023-11-16Update Cargo.lockPhilipp Krones-7/+5
2023-11-16Merge commit 'edb720b199083f4107b858a8761648065bf38d86' into clippyupPhilipp Krones-10369/+10338
2023-11-16Merge commit 'edb720b199083f4107b858a8761648065bf38d86' into clippyupPhilipp Krones-10369/+10338
2023-11-16Auto merge of #11823 - flip1995:rustup, r=flip1995bors-117/+102
Rustup r? `@ghost` changelog: none
2023-11-16Bump Clippy version -> 0.1.76Philipp Krones-5/+5
2023-11-16Bump nightly version -> 2023-11-16Philipp Krones-1/+1
2023-11-16Merge remote-tracking branch 'upstream/master' into rustupPhilipp Krones-10404/+10388
2023-11-16Auto merge of #3166 - devnexen:reallocarray, r=RalfJungbors-1/+48
reallocarray shim linux/freebsd support proposal.
2023-11-16Auto merge of #15830 - ↵bors-41/+23
davidbarsky:davidbarsky/allow-companion-extension-to-call-rust-analyzer, r=davidbarsky code: expose workspaces to other extensions; remove `addProject` command This (mostly red) PR does three things: - Exposes two methods to companion extensions (`setWorkspaces` and `notifyRustAnalyzer`). - `setWorkspaces` is needed to update `linkedProjects` _without_ writing workspace/global configuration. - `notifyRustAnalyzer` to get the server to pull the new configuration. - Makes `Ctx` implement `RustAnalyzerExtensionApi` to prevent accidental regressions. - Remove `rust-analyzer.addProject`, as that will live in a buck2 companion extension. No need for that to be in rust-analyzer! I can see the utility of combining `notifyRustAnalyzer` and `setWorkspaces` into a single method (`updateWorkspacesAndNotify()`?), but I don't feel strongly about this. My feeling is that this API could be easily changed in the future.
2023-11-16remove unused PhantomDataSarrus1-27/+29
2023-11-16code: expose workspaces to other extensions; remove `addProject` commandDavid Barsky-41/+23
2023-11-16reallocarray shim linux/freebsd support proposal.David Carlier-1/+48
2023-11-16Update documentation for `MAYBE_MISUSED_CFG` lintGuillaume Gomez-1/+7
2023-11-16Add UI test for mispelled `test`Guillaume Gomez-1/+49
2023-11-16Extend `maybe_misused_cfg` lint over `cfg(test)`Guillaume Gomez-0/+13
2023-11-16let-chain fmtEsteban Küber-2/+1
2023-11-16address review commentEsteban Küber-23/+20
2023-11-16recover primary span labelEsteban Küber-107/+131
2023-11-16Suggest `unwrap()` on field not found for `Result`/`Option`Esteban Küber-23/+166
When encountering a `Result<T, _>` or `Option<T>` where `T` has a field that's being accessed, suggest calling `.unwrap()` to get to the field.
2023-11-16Suggest field typo through derefsEsteban Küber-192/+227
Take into account implicit dereferences when suggesting fields. ``` error[E0609]: no field `longname` on type `Arc<S>` --> $DIR/suggest-field-through-deref.rs:10:15 | LL | let _ = x.longname; | ^^^^^^^^ help: a field with a similar name exists: `long_name` ``` CC https://github.com/rust-lang/rust/issues/78374#issuecomment-719564114
2023-11-16Add test for parens around match arm pattern and conditionEsteban Küber-0/+63
2023-11-16Smaller span for unnessary `mut` suggestionEsteban Küber-13/+12
2023-11-16Move tests to subdirectoryEsteban Küber-0/+0
2023-11-16allow more div and rem operations that can be checkedy21-45/+124
2023-11-16[`match_same_arms`]: respect allow attrs on armsy21-3/+5
2023-11-16Suggest replacing `Self` with the right type on type errorEsteban Küber-4/+27
When encountering a type error caused by the use of `Self`, suggest using the actual type name instead. ``` error[E0308]: mismatched types --> $DIR/struct-path-self-type-mismatch.rs:13:9 | LL | impl<T> Foo<T> { | - ------ this is the type of the `Self` literal | | | found type parameter LL | fn new<U>(u: U) -> Foo<U> { | - ------ expected `Foo<U>` because of return type | | | expected type parameter LL | / Self { LL | | LL | | inner: u LL | | LL | | } | |_________^ expected `Foo<U>`, found `Foo<T>` | = note: expected struct `Foo<U>` found struct `Foo<T>` = note: a type parameter was expected, but a different one was found; you might be missing a type parameter or trait bound = note: for more information, visit https://doc.rust-lang.org/book/ch10-02-traits.html#traits-as-parameters help: use the type name directly | LL | Foo::<U> { | ~~~~~~~~ ``` Fix #76086.
2023-11-16Point at impl self ty on type error involving `Self`Esteban Küber-1/+41
When encountering a type error involving a `Self` literal, point at the self type of the enclosing `impl`. CC #76086.
2023-11-16More detail when expecting expression but encountering bad macro argumentEsteban Küber-67/+200
Partially address #71039.
2023-11-16fix: better resolve assoc item with type boundaustaras-23/+156
2023-11-16Auto merge of #117956 - saethlin:provenance-gc-access, r=RalfJungbors-0/+7
Let Miri see the AllocId for all TyCtxt allocations Per https://github.com/rust-lang/miri/pull/3103#discussion_r1391589896 r? `@RalfJung`
2023-11-16fix missing assoc itemYoung-Flash-5/+18
2023-11-16ignore implied bounds with placeholdersAli MJ Al-Nasrawy-3/+81
2023-11-16Let Miri see the AllocId for all TyCtxt allocationsBen Kimock-0/+7
2023-11-16Auto merge of #117875 - Mark-Simulacrum:bootstrap-bump, r=clubby789bors-1130/+1250
Bootstrap bump Bumps bootstrap compiler to just-released beta. https://forge.rust-lang.org/release/process.html#master-bootstrap-update-t-2-day-tuesday
2023-11-16Auto merge of #117955 - notriddle:master, r=GuillaumeGomezbors-61/+10
rustdoc-search: simplify the checkTypes fast path This reduces code size while still matching the common case for plain, concrete types. This should not introduce any user-visible behavior changes. The perf impact of the change was evaluated using <https://gitlab.com/notriddle/rustdoc-js-profile>. The output of the tool can be found here: http://notriddle.com/rustdoc-html-demo-5/profile-1/index.html r? `@GuillaumeGomez`
2023-11-16Stabilize ptr_addr_eq library featureUrgau-5/+5
2023-11-16Auto merge of #3168 - RalfJung:set_var, r=RalfJungbors-5/+5
get rid of our last uses of set_var Fixes https://github.com/rust-lang/miri/issues/2783
2023-11-16get rid of our last uses of set_varRalf Jung-5/+5
2023-11-16Auto merge of #3167 - RalfJung:rustup, r=RalfJungbors-339/+878
Rustup
2023-11-16Merge from rustcRalf Jung-338/+877