| Age | Commit message (Collapse) | Author | Lines |
|
Stable release 1.26.0
|
|
|
|
[beta] Process backports
* https://github.com/rust-lang/rust/pull/50419: rustdoc: Resolve nested `impl Trait`s
* https://github.com/rust-lang/rust/pull/50474: Fix ICE in assertion macro
r? @Mark-Simulacrum
|
|
|
|
|
|
[beta] Revert "Implement FromStr for PathBuf"
This is a backport of https://github.com/rust-lang/rust/pull/50401
|
|
This reverts commit 05a9acc3b844ff284a3e3d85dde2d9798abfb215.
|
|
[beta] Yet another round of backports
* #50092: Warn on pointless `#[derive]` in more places
* #50227: Fix ICE with erroneous `impl Trait` in a trait impl
#50092 also needed some tweaks on the beta branch (see my own two commits).
r? @alexcrichton
|
|
* Changed `// compile-pass` to `// must-compile-successfully`
* Removed checks on unstable features
|
|
ExpansionKind::ForeignItems was added in #49350, which is not included
in the 1.26 beta.
|
|
Fixes #49841
|
|
This fixes the regression in #49934 and ensures that unused `#[derive]`s on statements, expressions and generic type parameters survive to trip the `unused_attributes` lint. For `#[derive]` on macro invocations it has a hardcoded warning since linting occurs after expansion. This also adds regression testing for some nodes that were already warning properly.
closes #49934
|
|
[Beta] Process backports
* #50257: Don't ICE on tuple struct ctor with incorrect arg count
|
|
|
|
[beta] More backports
* https://github.com/rust-lang/rust/pull/49368: Feature gate where clauses on associated types
* https://github.com/rust-lang/rust/pull/50253: drop elaboration should reveal all *(needs `beta-accepted` stamp)*
r? @alexcrichton
|
|
Fixes #49685
|
|
This used to happen by default as part of the normalization routine
that was being used.
|
|
|
|
|
|
[beta] Remove dependency on `parking_lot`
Unfortunately the `parking_lot` crate enables the `synchapi` feature of the
`winapi` crate which activates a dependency on `libsynchronization.a`. The MinGW
version of `libsynchronization.a` pulls in a dependency
`api-ms-core-synch-l1-2-0.dll` which causes rustc to not work on Windows 7
(tracked in #49438)
The `parking_lot` crate is not currently used in the compiler unless parallel
queries are enabled. This feature is not enabled by default and not used at all
in the beta/stable compilers. As a result the dependency in this commit was
removed and the CI build which checks parallel queries was disabled.
This isn't a great long-term solution but should hopefully be enough of a patch
for beta to buy us some more time to figure this out.
|
|
Unfortunately the `parking_lot` crate enables the `synchapi` feature of the
`winapi` crate which activates a dependency on `libsynchronization.a`. The MinGW
version of `libsynchronization.a` pulls in a dependency
`api-ms-core-synch-l1-2-0.dll` which causes rustc to not work on Windows 7
(tracked in #49438)
The `parking_lot` crate is not currently used in the compiler unless parallel
queries are enabled. This feature is not enabled by default and not used at all
in the beta/stable compilers. As a result the dependency in this commit was
removed and the CI build which checks parallel queries was disabled.
This isn't a great long-term solution but should hopefully be enough of a patch
for beta to buy us some more time to figure this out.
|
|
[beta] Backport #50072
* #50072: Allow variant discriminant initializers to refer to other initializers of the same enum
|
|
the same enum
|
|
[beta] Process backports
* https://github.com/rust-lang/rust/pull/49779: Don't report compile-time errors for promoteds
* https://github.com/rust-lang/rust/pull/50110: Warn on all erroneous constants
|
|
|
|
|
|
The error messages differ between optimized and nonoptimized mode
|
|
|
|
[beta] Another round of backports
This is a backport of:
* https://github.com/rust-lang/rust/pull/50039
* https://github.com/rust-lang/rust/pull/50121
|
|
[beta] Backport - Improve assertion in Query::force().
Follow up to https://github.com/rust-lang/rust/pull/49695#issuecomment-383214077
r? @alexcrichton
|
|
|
|
|
|
|
|
This reverts commit e53a2a72743810e05f58c61c9d8a4c89b712ad2e.
|
|
`()`, not `!`.
Note that this commit, since it is trying to be minimal in order to
ease backporting to the beta and release channels, does *not* include
the old future-proofing warnings that we used to have associated with
such fallback to `()`; see discussion at this comment:
https://github.com/rust-lang/rust/issues/49691#issuecomment-381266730
|
|
This commit is just covering the feature gate itself and the tests
that made direct use of `!` and thus need to opt back into the
feature.
A follow on commit brings back the other change that motivates the
revert: Namely, going back to the old rules for falling back to `()`.
|
|
and add one for non-mut slicing since I touched that method too
|
|
|
|
[beta] Tweak some stabilizations in libstd
This is a backport of https://github.com/rust-lang/rust/pull/50088
|
|
[beta] Processing merged backports
This is a backport of the following PRs:
* #49386
* #49465
* #49647
* #49692
* #49695
* #49714
* #49730
* #49830
* #49981
|
|
|
|
This commit papers over #49889 (introducing a fixme pointing at #50125) for a
bug that was introduced with #49695. This workaround is taken from #49891.
|
|
This builder is starting to time out frequently causing PRs to bounce and
otherwise doesn't seem to be catching too many bugs, so this commit removes it
entirely. We've had a number of timeouts in the last few weeks related to this
builder:
* https://travis-ci.org/rust-lang/rust/jobs/360947582
* https://travis-ci.org/rust-lang/rust/jobs/360464190
* https://travis-ci.org/rust-lang/rust/jobs/359946975
* https://travis-ci.org/rust-lang/rust/jobs/361213241
* https://travis-ci.org/rust-lang/rust/jobs/362346279
* https://travis-ci.org/rust-lang/rust/jobs/362072331
On a good run this builder takes about 2h15m, which is already too long for
Travis and the variable build times end up pushing it beyond the 3h limit
occasionally.
The timeouts here are somewhat expected in that an incrementally compiled rustc
compiler isn't optimized like a normal rustc, disallowing inlining between
codegen units and losing lots of optimization opportunities.
|
|
|
|
|
|
|
|
|
|
In intercrate mode, if we determine that a particular `T: Trait` is
unknowable, we sometimes also go and get extra causal information. An
errant `?` was causing us to propagate an error found in that process
out as if `T: Trait` was not unknowable but rather not provable. This
led to an ICE.
|
|
Fixes #49631
|
|
|