| Age | Commit message (Collapse) | Author | Lines |
|
cc [`?` tracking issue](https://github.com/rust-lang/rust/issues/31436)
|
|
Fix ICE test in compiletest fail-tests
While working on Clippy which uses *compiletest*, I noticed that as long as all expected error are found, *compile-fail* tests will be marked *ok* even if there is an ICE. One function seems to have not been updated with JSON errors because ICEs are now reported like this:
```json
{"message":"../src/librustc/ty/context.rs:161: Attempted to intern `_` which contains inference types/regions in the global type context","code":null,"level":"error: internal compiler error","spans":[],"children":[],"rendered":null}
```
I don't think I can add a test for that.
I guess:
r? @nikomatsakis
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Replace try! with ?.
|
|
|
|
|
|
|
|
|
|
|
|
Fix alignment for packed unions
Add some missing privacy test
Get rid of `unimplemented_unions` macro
|
|
|
|
- Fixes #35270
- Part of #35233
r? @jonathandturner
|
|
|
|
Update E0009 to new format
Part of #35233
Fixes #35193
r? @jonathandturner
|
|
Update E0005 to use a label
Fixes #35192 as Part of #35233
r? @jonathandturner
|
|
|
|
|
|
|
|
Implement the `!` type
This implements the never type (`!`) and hides it behind the feature gate `#[feature(never_type)]`. With the feature gate off, things should build as normal (although some error messages may be different). With the gate on, `!` is usable as a type and diverging type variables (ie. types that are unconstrained by anything in the code) will default to `!` instead of `()`.
|
|
r=jonathandturner
Update E0302 to the new format
Part of #35233.
Fixes #35523.
r? @jonathandturner
|
|
|
|
Split Ty::is_empty method into is_never and is_uninhabited
|
|
|
|
|
|
|
|
Do not span across nodes for E0004
Part of #35233.
Fixes #35529.
r? @arielb1
|
|
Update E0008 and E0007 to new format
Part of #35233
A fix for #35496
r? @jonathandturner
|
|
Rollup of 15 pull requests
- Successful merges: #35371, #35396, #35446, #35449, #35452, #35458, #35465, #35466, #35470, #35475, #35477, #35484, #35504, #35507, #35524
- Failed merges: #35395, #35415
|
|
r=jonathandturner
Turn on new errors and json mode
This PR is a big-switch, but on a well-worn path:
* Turns on new errors by default (and removes old skool)
* Moves json output from behind a flag
The RFC for new errors [landed](https://github.com/rust-lang/rfcs/pull/1644) and as part of that we wanted some bake time. It's now had a few weeks + all the time leading up to the RFC of people banging on it. We've also had [editors updating to the new format](https://github.com/saviorisdead/RustyCode/pull/159) and expect more to follow.
We also have an [issue on old skool](https://github.com/rust-lang/rust/issues/35330) that needs to be fixed as more errors are switched to the new style, but it seems silly to fix old skool errors when we fully intend to throw the switch in the near future.
This makes it lean towards "why not just throw the switch now, rather than waiting a couple more weeks?" I only know of vim that wanted to try to parse the new format but were not sure how, and I think we can reach out to them and work out something in the 8 weeks before this would appear in a stable release.
We've [hashed out](https://github.com/rust-lang/rust/issues/35330) stabilizing JSON output, and it seems like people are relatively happy making what we have v1 and then likely adding to it in the future. The idea is that we'd maintain backward compatibility and just add new fields as needed. We'll also work on a separate output format that'd be better suited for interactive tools like IDES (since JSON message can get a little long depending on the error).
This PR stabilizes JSON mode, allowing its use without `-Z unstable-options`
Combined, this gives editors two ways to support errors going forward: parsing the new error format or using the JSON mode. By moving JSON to stable, we can also add support to Cargo, which plugin authors tell us does help simplify their support story.
r? @nikomatsakis
cc @rust-lang/tools
Closes https://github.com/rust-lang/rust/issues/34826
|
|
|
|
Address ICEs running w/ incremental compilation and building glium
Fixes for various ICEs I encountered trying to build glium with incremental compilation enabled. Building glium now works. Of the 4 ICEs, I have test cases for 3 of them -- I didn't isolate a test for the last commit and kind of want to go do other things -- most notably, figuring out why incremental isn't saving much *effort*.
But if it seems worthwhile and I can come back and try to narrow down the problem.
r? @michaelwoerister
Fixes #34991
Fixes #32015
|
|
|
|
|
|
|
|
|
|
|
|
Err codes
r? @jonathandturner
|
|
Update E0004 to use labels
Fixes #35191 and is part of #35233
"r? @jonathandturner
|
|
Updated E0306 to new format.
Part of #35233.
Fixes #35315.
r? @jonathandturner
|
|
|
|
|
|
|
|
|