- 16 1月, 2018 1 次提交
-
-
由 Esteban Küber 提交于
- Properly address Variant Ctors - Show signature if span of trait method without `self` is not available
-
- 15 1月, 2018 5 次提交
-
-
由 Esteban Küber 提交于
-
由 Esteban Küber 提交于
-
由 Esteban Küber 提交于
-
由 Esteban Küber 提交于
-
由 Esteban Küber 提交于
-
- 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.
-
- 04 1月, 2018 2 次提交
-
-
由 Alex Crichton 提交于
These no longer work now that Cargo changes the cwd of rustc while it's running. Instead use an absolute path that's set by rustbuild.
-
由 Eduard-Mihai Burtescu 提交于
-
- 03 1月, 2018 1 次提交
-
-
由 Vadim Petrochenkov 提交于
-
- 21 12月, 2017 2 次提交
-
-
由 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.
-
由 Esteban Küber 提交于
-
- 18 12月, 2017 1 次提交
-
-
由 Esteban Küber 提交于
-
- 15 12月, 2017 2 次提交
-
-
由 Alex Burka 提交于
-
由 Alex Burka 提交于
-
- 14 12月, 2017 1 次提交
-
-
由 Jeffrey Seyfried 提交于
-
- 13 12月, 2017 2 次提交
-
-
由 Jeffrey Seyfried 提交于
-
由 Vadim Petrochenkov 提交于
-
- 10 12月, 2017 1 次提交
-
-
由 Jeffrey Seyfried 提交于
-
- 06 12月, 2017 2 次提交
-
-
由 Oliver Schneider 提交于
-
由 Jeffrey Seyfried 提交于
-
- 01 12月, 2017 4 次提交
-
-
由 Julian Kulesh 提交于
-
由 Sunjay Varma 提交于
Renaming MethodRibKind to TraitOrImplItemRibKind and removing its field which was never used. Lifting the HasTypeParameters rib to all trait item kinds and all impl item kinds
-
由 Sunjay Varma 提交于
-
由 Julian Kulesh 提交于
-
- 30 11月, 2017 1 次提交
-
-
由 Pietro Albini 提交于
This commit adds support for nested groups inside `use` declarations, such as `use foo::{bar, sub::{baz::Foo, *}};`.
-
- 29 11月, 2017 2 次提交
-
-
由 Jeffrey Seyfried 提交于
-
由 Julian Kulesh 提交于
-
- 24 11月, 2017 3 次提交
-
-
由 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.
-
由 Maxim Zholobak 提交于
-
- 23 11月, 2017 1 次提交
-
-
由 Maxim Zholobak 提交于
-
- 21 11月, 2017 2 次提交
-
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
-
- 20 11月, 2017 2 次提交
-
-
由 Oliver Schneider 提交于
-
由 Oliver Schneider 提交于
-
- 13 11月, 2017 1 次提交
-
-
由 Maxim Zholobak 提交于
-
- 09 11月, 2017 1 次提交
-
-
由 Esteban Küber 提交于
On the case of duplicated names caused by an `extern crate` statement with a rename, don't include the inline suggestion, instead using a span label with only the text to avoid incorrect rust code output.
-
- 05 11月, 2017 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 04 11月, 2017 1 次提交
-
-
由 Esteban Küber 提交于
When encountering a let binding type error, attempt to parse as initializer instead. If successful, it is likely just a typo: ```rust fn main() { let x: Vec::with_capacity(10); } ``` ``` error: expected type, found `10` --> file.rs:3:31 | 3 | let x: Vec::with_capacity(10, 20); | -- ^^ | || | |help: did you mean assign here?: `=` | while parsing the type for `x` ```
-