- 01 3月, 2018 1 次提交
-
-
由 Vadim Petrochenkov 提交于
Improve recovery for trailing comma after `..`
-
- 24 2月, 2018 1 次提交
-
-
由 Vadim Petrochenkov 提交于
-
- 17 2月, 2018 2 次提交
-
-
由 Seiichi Uchida 提交于
-
由 Seiichi Uchida 提交于
This span covers the whole visibility expression: e.g. `pub (in path)`.
-
- 23 1月, 2018 2 次提交
-
-
由 John Kåre Alsaker 提交于
Adds support for immovable generators. Move checking of invalid borrows across suspension points to borrowck. Fixes #44197, #45259 and #45093.
-
由 Vadim Petrochenkov 提交于
-
- 13 1月, 2018 1 次提交
-
-
由 leonardo.yvens 提交于
No longer parse it. Remove AutoTrait variant from AST and HIR. Remove backwards compatibility lint. Remove coherence checks, they make no sense for the new syntax. Remove from rustdoc.
-
- 21 12月, 2017 1 次提交
-
-
由 Jonas Platte 提交于
The Generics now contain one Vec of an enum for the generic parameters, rather than two separate Vec's for lifetime and type parameters. Additionally, places that previously used Vec<LifetimeDef> now use Vec<GenericParam> instead.
-
- 15 12月, 2017 1 次提交
-
-
由 Alex Burka 提交于
-
- 06 12月, 2017 1 次提交
-
-
由 Oliver Schneider 提交于
-
- 30 11月, 2017 1 次提交
-
-
由 Pietro Albini 提交于
This commit adds support for nested groups inside `use` declarations, such as `use foo::{bar, sub::{baz::Foo, *}};`.
-
- 24 11月, 2017 2 次提交
-
-
由 Esteban Küber 提交于
Try to identify the following code in order to provide better diagnostics, but return the error to bail out early during the parse.
-
由 Esteban Küber 提交于
When encountering `pub ident`, attempt to identify the code that comes afterwards, wether it is a brace block (assume it is a struct), a paren list followed by a colon (assume struct) or a paren list followed by a block (assume a fn). Consume those blocks to avoid any further parser errors and return a `Placeholder` item in order to allow the parser to continue. In the case of unenclosed blocks, the behavior is the same as it is currently: no further errors are processed.
-
- 04 11月, 2017 2 次提交
-
-
由 leonardo.yvens 提交于
Adds an `IsAuto` field to `ItemTrait` which flags if the trait was declared as an `auto trait`. Auto traits cannot have generics nor super traits.
-
由 leonardo.yvens 提交于
DefaultImpl is a highly confusing name for what we now call auto impls, as in `impl Send for ..`. The name auto impl is not formally decided but for sanity anything is better than `DefaultImpl` which refers neither to `default impl` nor to `impl Default`.
-
- 28 10月, 2017 1 次提交
-
-
由 Paul Lietar 提交于
-
- 26 10月, 2017 1 次提交
-
-
由 sinkuu 提交于
-
- 23 10月, 2017 1 次提交
-
-
由 sinkuu 提交于
-
- 18 10月, 2017 2 次提交
-
-
由 Sunjay Varma 提交于
-
由 Sunjay Varma 提交于
Lifting Generics from MethodSig to TraitItem and ImplItem since we want to support generics in each variant of TraitItem and ImplItem
-
- 14 10月, 2017 1 次提交
-
-
由 Vadim Petrochenkov 提交于
-
- 28 7月, 2017 2 次提交
-
-
由 Alex Crichton 提交于
-
由 John Kåre Alsaker 提交于
-
- 10 7月, 2017 1 次提交
-
-
由 Vadim Petrochenkov 提交于
-
- 25 5月, 2017 2 次提交
-
-
由 Jeffrey Seyfried 提交于
-
由 Jeffrey Seyfried 提交于
-
- 13 5月, 2017 2 次提交
-
-
由 est31 提交于
-
由 Andre Bogus 提交于
This is mostly removing stray ampersands, needless returns and lifetimes.
-
- 12 5月, 2017 1 次提交
-
-
由 Nick Cameron 提交于
-
- 24 4月, 2017 1 次提交
-
-
由 Gianni Ciccarelli 提交于
this commit implements the first step of the `default impl` feature: all items in a `default impl` are (implicitly) `default` and hence specializable. In order to test this feature I've copied all the tests provided for the `default` method implementation (in run-pass/specialization and compile-fail/specialization directories) and moved the `default` keyword from the item to the impl. See referenced issue for further info
-
- 13 4月, 2017 1 次提交
-
-
由 A.J. Gardner 提交于
-
- 03 4月, 2017 1 次提交
-
-
由 Esteban Küber 提交于
Add a `TyErr` type to represent unknown types in places where parse errors have happened, while still able to build the AST. Initially only used to represent incorrectly written fn arguments and avoid "expected X parameters, found Y" errors when called with the appropriate amount of parameters. We cannot use `TyInfer` for this as `_` is not allowed as a valid argument type. Example output: ```rust error: expected one of `:` or `@`, found `,` --> file.rs:12:9 | 12 | fn bar(x, y: usize) {} | ^ error[E0061]: this function takes 2 parameters but 3 parameters were supplied --> file.rs:19:9 | 12 | fn bar(x, y) {} | --------------- defined here ... 19 | bar(1, 2, 3); | ^^^^^^^ expected 2 parameters ```
-
- 12 3月, 2017 1 次提交
-
-
由 Taylor Cramer 提交于
-
- 11 3月, 2017 1 次提交
-
-
由 Jeffrey Seyfried 提交于
-
- 25 2月, 2017 1 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
- 19 1月, 2017 1 次提交
-
-
由 Oliver Schneider 提交于
-
- 17 1月, 2017 3 次提交
-
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
-
- 16 1月, 2017 1 次提交
-
-
由 Scott Olson 提交于
This is a clearer name since they represent [a, b, c] array literals.
-