https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.26.2 2018-04-22T00:05:10+00:00 2018-04-22T00:05:10+00:00 Felix S. Klock II pnkfelix@pnkfx.org 2018-04-20T15:07:58+00:00 urn:sha1:1bc69894fc86e7a0b2bdcdda05f04ff1897bc640 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 `()`. 2018-03-14T04:44:51+00:00 Andrew Cann shum@canndrew.org 2018-01-21T08:44:41+00:00 urn:sha1:a9fc3901b07d0494bd3eb9c37b10e63b429714b0 Replace feature(never_type) with feature(exhaustive_patterns). feature(exhaustive_patterns) only covers the pattern-exhaustives checks that used to be covered by feature(never_type) 2017-08-08T16:30:26+00:00 kennytm kennytm@gmail.com 2017-08-08T15:28:09+00:00 urn:sha1:3cb23a714f2b7adbf1eee697fb6471c4dd733f04 Fix #43162, fix #43727. 2017-05-17T19:34:37+00:00 Pietro Albini pietro@pietroalbini.org 2017-05-15T20:11:16+00:00 urn:sha1:93c1f2472bd627955e44970de075c2e90f246501 2017-02-18T20:28:44+00:00 Taylor Cramer cramertaylorj@gmail.com 2017-02-16T07:28:59+00:00 urn:sha1:4d65622dcd3be66ec53656c499afe7bbc8aa1ae7 2017-02-18T02:58:32+00:00 Taylor Cramer cramertaylorj@gmail.com 2017-02-15T22:52:27+00:00 urn:sha1:5205e2f8b8094a5f3d0205593820391dfe481808 2016-11-22T04:20:42+00:00 Geoffry Song goffrie@gmail.com 2016-10-29T22:15:06+00:00 urn:sha1:9d42549df40464899dda11fc9509f511046fb4c6 This implements RFC 1624, tracking issue #37339. - `FnCtxt` (in typeck) gets a stack of `LoopCtxt`s, which store the currently deduced type of that loop, the desired type, and a list of break expressions currently seen. `loop` loops get a fresh type variable as their initial type (this logic is stolen from that for arrays). `while` loops get `()`. - `break {expr}` looks up the broken loop, and unifies the type of `expr` with the type of the loop. - `break` with no expr unifies the loop's type with `()`. - When building MIR, `loop` loops no longer construct a `()` value at termination of the loop; rather, the `break` expression assigns the result of the loop. `while` loops are unchanged. - `break` respects contexts in which expressions may not end with braced blocks. That is, `while break { break-value } { while-body }` is illegal; this preserves backwards compatibility. - The RFC did not make it clear, but I chose to make `break ()` inside of a `while` loop illegal, just in case we wanted to do anything with that design space in the future. This is my first time dealing with this part of rustc so I'm sure there's plenty of problems to pick on here ^_^