| Age | Commit message (Collapse) | Author | Lines |
|---|
|
|
|
|
|
Clearer use of the error message and span labels to communicate
duplicaiton defitions/imports.
New error format:
```
error[E0428]: the name `Foo` is defined twice
--> example.rs:2:1
|
1 | trait Foo { }
| ------------- previous definition of the trait `Foo` here
2 | struct Foo { }
| ^^^^^^^^^^^^^^ `Foo` redefined here
= note: `Foo` must be defined only once in the type namespace of this module
error: aborting due to previous error
```
|
|
Merge crate `collections` into `alloc`
This is a necessary step in order to merge #42565
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For code like `if x = 3 {}`, output:
```
error[E0308]: mismatched types
--> $DIR/issue-17283.rs:25:8
|
25 | if x = x {
| ^^^^^
| |
| help: did you mean to compare equality? `x == x`
| expected bool, found ()
|
= note: expected type `bool`
found type `()`
```
|
|
|
|
Instead of suppressing only trait errors that are "exact duplicates",
display only the "most high-level" error when there are multiple trait
errors with the same span that imply each-other.
e.g. when there are both `[closure]: Fn` and `[closure]: FnOnce`, omit
displaying the `[closure]: FnOnce` bound.
|
|
|
|
Build instruction profiler runtime as part of compiler-rt
r? @alexcrichton
This is #38608 with some fixes.
Still missing:
- [x] testing with profiler enabled on some builders (on which ones? Should I add the option to some of the already existing configurations, or create a new configuration?);
- [x] enabling distribution (on which builders?);
- [x] documentation.
|
|
|
|
|
|
Doesnt' seem to add much value, and since we don't track
`TransCrateItem` anymore, it's not clear what to translate it to.
|
|
In the case of `TransCrateItem`, I had to tweak the tests a bit, but
it's a concept that doesn't work well under new system.
|
|
|
|
Add E0609
Part of #42229.
cc @Susurrus
|
|
|
|
|
|
Currently `use foo::self;` would emit both E0429 and E0432. This
commit silence the latter one (assuming `foo` is a valid module).
Fixes #42559
|
|
Ignore variadic FFI test on AArch64
I've cross compiled Rust to `aarch64-linux-gnu`, and tried to run the compile-fail tests, but `variadic-ffi.rs` fails with the following error:
```
The ABI `"stdcall"` is not supported for the current target [E0570]
```
The test seems to be ignored on (32-bit) ARM, so I turned it off for AArch64 too.
|
|
|
|
Changing error message from `contains interior mutability` to `may contain interior mutability`
Fixes #40313 . I have changed the message from `contains interior mutability` to `may contain interior mutability` for the following example
```
use std::cell::Cell;
use std::panic::catch_unwind;
fn main() {
let mut x = Cell::new(22);
catch_unwind(|| { x.set(23); });
}
```
which has been added as a ui test.
Also, the message [here](https://github.com/gaurikholkar/rust/blob/master/src/librustc_mir/transform/qualify_consts.rs#L666) and it's respective `compile-fail` test have been modified.
cc @nikomatsakis @Mark-Simulacrum @eddyb
|
|
Remove 'elided' from lifetime resolution error
Removes 'elided' from lifetime resolution errors
Removes 'elided' from relevant error messaging tests
This PR resolves https://github.com/rust-lang/rust/issues/29094
r? @Mark-Simulacrum
|
|
Add E0602
Part of #42229.
cc @Susurrus
|
|
|
|
Use multiline note for trait suggestion
|
|
|
|
|
|
Change for-loop desugar to not borrow the iterator during the loop
This is enables the use of suspend points inside for-loops in movable generators. This is illegal in the current desugaring as `iter` is borrowed across the body.
|
|
Better suggestion for unknown method
r? @Manishearth
fixes #42386
|
|
Add E0603 error code
Part of #42229.
cc @Susurrus
|
|
Removes 'elided' from lifetime resolution errors
Removes 'elided' from relevant error messaging tests
|
|
Extend the unused macro lint to macros 2.0
Extends the unused macro lint (added in PR #41907) to macros 2.0 (added in PR #40847).
r? @jseyfried
|
|
rustc: remove temporary lifetime extension by borrow hint
closes #39283.
Thanks to @nikomatsakis for mentoring on this one.
r? @arielb1
|
|
|
|
Fixes #42386
|
|
|
|
|
|
|
|
|
|
now we grow the type-sizes info during execution, rather than walking
the cache after the fact
|
|
|
|
associated_consts: check trait obligations and regionck for associated consts
Closes #41323
r? @nikomatsakis
|
|
|
