| Age | Commit message (Collapse) | Author | Lines |
|
|
|
Handle more cases of typos misinterpreted as type ascription
Fix #60933, #54516.
CC #47666, #34255, #48016.
|
|
fakenine:normalize_use_of_backticks_compiler_messages_p10, r=Centril
normalize use of backticks in compiler messages for librustc_lint
https://github.com/rust-lang/rust/issues/60532
|
|
|
|
Once again, the difference is in the test construction, it is ignored in compare-mode NLL and tested manually with revisions, and fails because the `migrate` revision is ran with `-Zpolonius`. There is no actual difference in the errors output by NLLs and Polonius.
|
|
|
|
|
|
resolve: Improve candidate search for unresolved macro suggestions
Use same scope visiting machinery for both collecting suggestion candidates and actually resolving the names.
The PR is better read in per-commit fashion with whitespace changes ignored (the first commit in particular moves some code around).
This should be the last pre-requisite for https://github.com/rust-lang/rust/pull/62086.
r? @davidtwco
|
|
Given
```
mented on Jan 26, 2015 •
trait Foo { fn method(&self) {} }
fn call_method<T>(x: &T) {
x.method()
}
```
suggest constraining `T` with `Foo`.
|
|
fakenine:normalize_use_of_backticks_compiler_messages_p7, r=alexreg
normalize use of backticks in compiler messages for librustc/lint
https://github.com/rust-lang/rust/issues/60532
|
|
Update the help message on error for self type
Fix #62609
|
|
Check that trait is exported or public before adding hint
Closes #62194.
This PR checks the `AccessLevels` of a trait to check whether adding the intercrate ambiguity hint is valid or not.
I am unsure of both the use of `.unwrap()` as well as removing hints for [downstream *and* [upstream](https://github.com/rust-lang/rust/blob/92b0f52584c9375505ecdefdd7855b93a5919d51/src/librustc/traits/select.rs#L112-L142).
|
|
|
|
|
|
Normally `#![feature(...)]` shouldn't change behavior, but custom attributes in particular are in the process of retirement, and we should not produce a message telling to enable them.
It also helps with unifying diagnostics for unresolved macros.
|
|
|
|
discussion https://github.com/rust-lang/rust/issues/50264
|
|
https://github.com/rust-lang/rust/issues/60532
|
|
fakenine:normalize_use_of_backticks_compiler_messages_p6, r=eddyb
normalize use of backticks in compiler messages for libsyntax/parse
https://github.com/rust-lang/rust/issues/60532
|
|
|
|
|
|
https://github.com/rust-lang/rust/issues/60532
|
|
|
|
Use snippet instead of pprinting statement
Fix #62554.
|
|
Improve diagnostics for invalid mutation through overloaded operators
Closes #58864
Closes #52941
Closes #57839
|
|
|
|
|
|
pnkfelix:issue-62614-downgrade-indirect-structural-match-lint-to-allow, r=zackmdavis
downgrade indirect_structural_match lint to allow
This is a short-term band-aid for the regression aspect of #62614.
|
|
Correctly break out of recovery loop
Fix #61858.
|
|
Add test for #49919
Closes #49919
|
|
|
|
|
|
r=eddyb
Dont recur infinitely from print_def_path
Fix #61711
|
|
|
|
pnkfelix:issue-61188-use-visitor-for-structural-match-check, r=nikomatsakis
use visitor for #[structural_match] check
This changes the code so that we recur down the structure of a type of a const (rather than just inspecting at a shallow one or two levels) when we are looking to see if it has an ADT that did not derive `PartialEq` and `Eq`.
Fix #61188
Fix #62307
Cc #62336
|
|
fakenine:normalize_use_of_backticks_compiler_messages_p4, r=Centril
normalize use of backticks in compiler messages for libsyntax/feature_gate.rs
https://github.com/rust-lang/rust/issues/60532
|
|
Raise the default recursion limit to 128
The previous limit of 64 is being (just) barely hit by genuine code out there, which is causing issues like https://github.com/rust-lang/rust/issues/62059 to rear their end.
Ideally, we wouldn’t have such arbitrary limits at all, but while we do, it makes a lot of sense to just raise this limit whenever genuine use-cases end up hitting it.
r? @pnkfelix
Fixes https://github.com/rust-lang/rust/issues/62059
|
|
https://github.com/rust-lang/rust/issues/60532
|
|
|
|
The regression tests explore:
(direct | indirect | doubly-indirect | unsafe) x (embedded | param):
where:
embedded: `struct Wrapper(... NoDerive ...);`
param: `struct Wrapper<X>(... X ...);`
direct: `const A: Wrapper<...> = Wrapper(NoDerive);`
indirect: `const A: & & Wrapper<...> = Wrapper(NoDerive)`
doubly-indirect: `const A: & & Wrapper<...> = & & Wrapper(& & NoDerive)`
unsafe: `const A: UnsafeWrap<...> = UnsafeWrap(std::ptr::null())`
|
|
|
|
|
|
https://github.com/rust-lang/rust/issues/60532
r? @alexreg
|
|
[let_chains, 3/6] And then there was only Loop
Here we remove `hir::ExprKind::While`.
Instead, we desugar: `'label: while $cond $body` into:
```rust
'label: loop {
match DropTemps($cond) {
true => $body,
_ => break,
}
}
```
Per https://github.com/rust-lang/rust/issues/53667#issuecomment-471583239.
This is a follow up to https://github.com/rust-lang/rust/pull/59288 which did the same for `if` expressions.
r? @matthewjasper
|
|
|
|
Add test for ICE #62375
Fixes #62375
|
|
|
|
Fixes #62375
|
|
Migrate `compile-pass` annotations to `build-pass`
This is a part of #62277.
As a first step, the `compile-pass` tests are migrated to `build-pass`.
r? @cramertj
cc @Centril
|
|
|