- 28 1月, 2017 2 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
- 19 1月, 2017 1 次提交
-
-
由 Oliver Schneider 提交于
-
- 17 1月, 2017 4 次提交
-
-
由 Jeffrey Seyfried 提交于
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
-
- 04 1月, 2017 1 次提交
-
-
由 comex 提交于
-
- 28 12月, 2016 5 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
- 22 12月, 2016 2 次提交
-
-
由 Jeffrey Seyfried 提交于
-
由 Jeffrey Seyfried 提交于
-
- 29 11月, 2016 1 次提交
-
-
由 Florian Diebold 提交于
-
- 28 11月, 2016 6 次提交
-
-
由 Eduard Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
- 22 11月, 2016 2 次提交
-
-
由 Geoffry Song 提交于
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 ^_^
-
由 Nicholas Nethercote 提交于
This changes structures like this: ``` [ ExprArray | 8 | P ] | v [ P | P | P | P | P | P | P | P ] | v [ ExprTup | 2 | P ] | v [ P | P ] | v [ Expr ] ``` to this: ``` [ ExprArray | 8 | P ] | v [ [ ExprTup | 2 | P ] | ... ] | v [ Expr | Expr ] ```
-
- 21 11月, 2016 2 次提交
-
-
由 Jeffrey Seyfried 提交于
-
由 Jeffrey Seyfried 提交于
-
- 18 11月, 2016 1 次提交
-
-
由 Niko Matsakis 提交于
Also simplify some of the `ty::AssociatedItem` representation, in particular by folding `has_value` into `hir::Defaultness`
-
- 17 11月, 2016 2 次提交
-
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
This commit does not change how the incremental accounting is done, so changes (or accessses) to an impl-item are still tagged to the enclosing impl. This commits adds the "main guts" of this change. It does not build on its own.
-
- 10 11月, 2016 1 次提交
-
-
由 Eduard Burtescu 提交于
-
- 27 10月, 2016 1 次提交
-
-
由 Eduard Burtescu 提交于
-
- 29 9月, 2016 1 次提交
-
-
由 Jonas Schievink 提交于
-
- 12 9月, 2016 1 次提交
-
-
由 Ahmed Charles 提交于
-
- 03 9月, 2016 1 次提交
-
-
由 Vadim Petrochenkov 提交于
-
- 22 8月, 2016 1 次提交
-
-
由 Jeffrey Seyfried 提交于
and refacotor `hir::PathListItem_::Ident` -> `hir::PathListItem_`.
-
- 19 8月, 2016 1 次提交
-
-
由 Guillaume Gomez 提交于
-
- 13 8月, 2016 3 次提交
-
-
由 Andrew Cann 提交于
Split Ty::is_empty method into is_never and is_uninhabited
-
由 Andrew Cann 提交于
Replace FnOutput with Ty Replace FnConverging(ty) with ty Purge FnDiverging, FunctionRetTy::NoReturn and FunctionRetTy::None
-
由 Andrew Cann 提交于
Add `TyKind::Empty` and fix resulting build errors.
-
- 12 8月, 2016 1 次提交
-
-
由 Eduard Burtescu 提交于
-