[beta]: Prepare the 1.31.0 beta release #55405
Commits on Oct 29, 2018
-
[beta]: Prepare the 1.31.0 stable release
* Update to Cargo's branched 1.31.0 branch * Update bootstrap compiler to stable 1.30.0 * Update the channel to `beta`
-
-
We're gonna link to nightly as this didn't make it into the corresponding stable.
-
-
This commit reduces the size of `Statement` from 80 bytes to 56 bytes on 64-bit platforms, by boxing the `AscribeUserType` variant of `StatementKind`. This change reduces instruction counts on most benchmarks by 1--3%.
-
Remove
PlaceContextfrom API ofmir::Visitor::visit_projection_elem.It is unused, and would not make sense to maintain in the commits later in this PR.
-
Refactoring: added
PatternTypeAnnotationwrapper around `UserTypeAn……notation` to ease future changes.
-
Added
mir::UserTypeProjection, a stub for a structure that projects…… *into* a given UserTypeAnnotation. (That is, it will pull out some component type held or referenced by the type annotation.) Note: this still needs to actually do projection itself. That comes in a later commit
-
Checkpoint: Added abstraction over collection of projections into use…
…r type. I did not think I would need this in the MIR, but in general local decls are going to need to support this. (That, or we need to be able define a least-upper-bound for a collection of types encountered via the pattern compilation.)
-
Add the actual chain of projections to
UserTypeProjection.Update the existing NLL `patterns.rs` test accordingly. includes changes addressing review feedback: * Added example to docs for `UserTypeProjections` illustrating how we build up multiple projections when descending into a pattern with type ascriptions. * Adapted niko's suggested docs for `UserTypeProjection`. * Factored out `projection_ty` from more general `projection_ty_core` (as a drive-by, made its callback an `FnMut`, as I discovered later that I need that). * Add note to docs that `PlaceTy.field_ty(..)` does not normalize its result. * Normalize as we project out `field_ty`.
-
Update mir-opt tests to reflect change to
AscribeUserTypeto carry ……a `UserTypeProjection`.
-
-
Add test for normalization during field-lookup on patterns with ascri…
…bed types. As a drive-by, also added test analogous to existing static_to_a_to_static_through_tuple, but now apply to a struct instead of a tuple.
-
Add intern table for
List<ProjectionElem<'tcx, (), ()>>.Also added alias `ProjectionKind<'tcx>` for `ProjectionElem<'tcx, (), ()>`.
-
Further foundational stuff on
ProjectionKindbefore I add it to `As……cribeUserType`.
-
-
-
resolve: Absolute paths may be undetermined on 2018 edition
due to macro-expanded `extern crate` items adding names to extern prelude.
-
-
resolve: Make sure macros and imports are resolved in full parent scope
Slightly simplify `fn build_reduced_graph_for_use_tree`
-
resolve: Desugar empty import groups into synthetic dummy imports
so that they are correctly resolved on 2018 edition
-
Fix ordering of nested modules in non-mod.rs mods
Flatten relative offset into directory path before adding inline (mod x { ... }) module names to the current directory path. Fix rust-lang#55094 -
Add note linking to Rust 2018 path semantics docs.
This commit extends existing path suggestions to link to documentation on the changed semantics of `use` in Rust 2018.
-
back out bogus
Ok-wrapping suggestion on?arm type mismatchThis suggestion was introduced in rust-lang#51938 / 6cc78bf (while introducing different language for type errors coming from `?` rather than a `match`), but it has a lot of false-positives (as repeatedly reported in Issues rust-lang#52537, rust-lang#52598, rust-lang#54578, rust-lang#55336), and incorrect suggestions carry more badness than marginal good suggestions do goodness. Just get rid of it (unless and until someone figures out how to do it correctly). Resolves rust-lang#52537, resolves rust-lang#54578.
-
