summary refs log tree commit diff
AgeCommit message (Collapse)AuthorLines
2018-06-01Auto merge of #51258 - Mark-Simulacrum:stable-next, r=nikomatsakis 1.26.2bors-71/+139
1.26.2 release This includes a backport of #51235 which fixes #51117 on stable. It has not been tested. r? @nikomatsakis since the backport was not clean. cc @rust-lang/core @rust-lang/release
2018-06-01Update version to 1.26.2Mark Simulacrum-1/+1
2018-06-01Update release notes for 1.26.2Mark Simulacrum-0/+10
2018-06-01change `PointerKind::Implicit` to a noteNiko Matsakis-70/+128
`PointerKind` is included in `LoanPath` and hence forms part of the equality check; this led to having two unequal paths that both represent `*x`, depending on whether the `*` was inserted automatically or explicitly. Bad mojo. The `note` field, in contrast, is intended more-or-less primarily for this purpose of adding extra data.
2018-05-25Auto merge of #51045 - Mark-Simulacrum:stable-point, r=alexcrichton 1.26.1bors-106/+545
Stable point release (1.26.1) This includes all items on [the wishlist](https://github.com/rust-lang/rust/issues/50756), plus https://github.com/rust-lang/rust/pull/50694, which backported cleanly. The target date is May 29th, Tuesday next week. cc @rust-lang/compiler @oli-obk @eddyb -- I backported https://github.com/rust-lang/rust/pull/50812, but it wasn't a clean patch so review would be appreciated.
2018-05-25Bump for 1.26.1Mark Simulacrum-1/+1
2018-05-25Add release notes for 1.26.1Mark Simulacrum-0/+24
2018-05-25Fix 07c42af554c to work on stableMark Simulacrum-11/+28
2018-05-25prohibit turbofish in `impl Trait` methodsNiko Matsakis-30/+74
2018-05-24Update RLS and RustfmtNick Cameron-54/+39
2018-05-24Fix self referential impl Trait substitutionsleonardo.yvens-2/+42
A high impact bug because a lot of common traits use a `Self` substitution by default. Should be backported to beta. There was a check for this which wasn't catching all cases, it was made more robust. Fixes #49376 Fixes #50626 r? @petrochenkov
2018-05-24Fix issue #50811 (`NaN > NaN` was true).kennytm-7/+71
Fix #50811 Make sure the float comparison output is consistent with the expected behavior when NaN is involved. ---- Note: This PR is a **BREAKING CHANGE**. If you have used `>` or `>=` to compare floats, and make the result as the length of a fixed array type, like: ```rust use std::f64::NAN; let x: [u8; (NAN > NAN) as usize] = [1]; ``` then the code will no longer compile. Previously, all float comparison involving NaN will just return "Greater", i.e. `NAN > NAN` would wrongly return `true` during const evaluation. If you need to retain the old behavior (why), you may replace `a > b` with `a != a || b != b || a > b`.
2018-05-24Update release notes for 1.26Mark Simulacrum-0/+206
2018-05-24Fix `fn main() -> impl Trait` for non-`Termination` traitleonardo.yvens-7/+44
Fixes #50595. This bug currently affects stable. Why I think we can go for hard error: - It will in stable for at most one cycle and there is no legitimate reason to abuse it, nor any known uses in the wild. - It only affects `bin` crates (which have a `main`), so there is little practical difference between a hard error or a deny lint, both are a one line fix. The fix was to just unshadow a variable. Thanks @nikomatsakis for the mentoring! r? @nikomatsakis
2018-05-24Filter out missing components from manifestsAlex Crichton-0/+22
This commit updates our manifest generation for rustup to filter out any components/extensions which are actually missing. This is intended to help mitigate #49462 by making the manifests reflect reality, that many targets now are missing a `rust-docs` component rather than requiring it exists.
2018-05-07Auto merge of #50510 - Mark-Simulacrum:stable, r=Mark-Simulacrum 1.26.0bors-1/+1
Stable release 1.26.0
2018-05-07Stable release 1.26.0Mark Simulacrum-1/+1
2018-05-06Auto merge of #50478 - pietroalbini:beta-backports, r=kennytmbors-89/+64
[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
2018-05-06Fix assertion message generationShotaro Yamada-58/+25
2018-05-06rustdoc: Resolve nested `impl Trait`sShotaro Yamada-31/+39
2018-05-03Auto merge of #50402 - alexcrichton:beta-next, r=sfacklerbors-27/+0
[beta] Revert "Implement FromStr for PathBuf" This is a backport of https://github.com/rust-lang/rust/pull/50401
2018-05-02Revert "Implement FromStr for PathBuf"Alex Crichton-27/+0
This reverts commit 05a9acc3b844ff284a3e3d85dde2d9798abfb215.
2018-04-30Auto merge of #50334 - pietroalbini:beta-backports, r=alexcrichtonbors-18/+179
[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
2018-04-30Adapt ui test of #50092 to betaPietro Albini-27/+10
* Changed `// compile-pass` to `// must-compile-successfully` * Removed checks on unstable features
2018-04-30Remove new enum variant from #50092 backportPietro Albini-9/+0
ExpansionKind::ForeignItems was added in #49350, which is not included in the 1.26 beta.
2018-04-30Do not ICE on generics mismatch with non-local traitsShotaro Yamada-2/+12
Fixes #49841
2018-04-30Warn on pointless `#[derive]` in more placesAustin Bonander-16/+193
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
2018-04-28Auto merge of #50298 - pietroalbini:beta-backports, r=oli-obkbors-1/+28
[Beta] Process backports * #50257: Don't ICE on tuple struct ctor with incorrect arg count
2018-04-28Don't ICE on tuple struct ctor with incorrect arg countEsteban Küber-1/+28
2018-04-27Auto merge of #50274 - pietroalbini:beta-backports, r=alexcrichtonbors-10/+69
[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
2018-04-27add regression testNiko Matsakis-0/+22
Fixes #49685
2018-04-27use `reveal_all` during drop elaborationNiko Matsakis-2/+4
This used to happen by default as part of the normalization routine that was being used.
2018-04-27improved debug outputNiko Matsakis-3/+11
2018-04-27Feature gate where clauses on associated typesMatthew Jasper-5/+32
2018-04-26Auto merge of #50254 - alexcrichton:beta-next, r=Mark-Simulacrumbors-9/+0
[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.
2018-04-26[beta] Remove dependency on `parking_lot`Alex Crichton-9/+0
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.
2018-04-26Auto merge of #50248 - pietroalbini:beta-backports, r=eddybbors-54/+148
[beta] Backport #50072 * #50072: Allow variant discriminant initializers to refer to other initializers of the same enum
2018-04-26Allow variant discriminant initializers to refer to other initializers of ↵Oliver Schneider-54/+148
the same enum
2018-04-25Auto merge of #50224 - pietroalbini:beta-backports, r=alexcrichtonbors-100/+357
[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
2018-04-25Rename ui test flag compile-pass to must-compile-successfullyPietro Albini-6/+6
2018-04-25Warn on all erroneous constantsOliver Schneider-75/+233
2018-04-25always optimize testOliver Schneider-1/+1
The error messages differ between optimized and nonoptimized mode
2018-04-25Only warn on erroneous promoted constantsOliver Schneider-30/+129
2018-04-23Auto merge of #50182 - alexcrichton:beta-next, r=alexcrichtonbors-55/+221
[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
2018-04-23Auto merge of #50175 - michaelwoerister:backport-e31dae4, r=alexcrichtonbors-1/+10
[beta] Backport - Improve assertion in Query::force(). Follow up to https://github.com/rust-lang/rust/pull/49695#issuecomment-383214077 r? @alexcrichton
2018-04-23TryFrom destabilization fixupsAlex Crichton-1/+2
2018-04-23Improve assertion in Query::force().Michael Woerister-1/+10
2018-04-21Add back missing `#![feature(never_type)]`skennytm-0/+17
2018-04-21Revert "Stabilize the TryFrom and TryInto traits"Felix S. Klock II-27/+27
This reverts commit e53a2a72743810e05f58c61c9d8a4c89b712ad2e.
2018-04-21Bring back old fallback semantics: Without feature(never_type), fallback to ↵Felix S. Klock II-5/+18
`()`, 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
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-10 14:49:00 +0000