- 03 10月, 2018 1 次提交
-
-
由 ljedrz 提交于
-
- 30 9月, 2018 1 次提交
-
-
由 Zack M. Davis 提交于
This seemed like a good way to kick the tires on the elided-lifetimes-in-paths lint (#52069)—seems to work! This was also pretty tedious—it sure would be nice if `cargo fix` worked on this codebase (#53896)!
-
- 28 9月, 2018 1 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
- 23 9月, 2018 1 次提交
-
-
由 Ariel Ben-Yehuda 提交于
During metadata loading, the AdtDefs for every ADT in the universe need to be loaded (for example, for coherence of builtin traits). For that, the attributes of the AdtDef need to be loaded too. The attributes of a struct are duplicated between 2 def ids - the constructor def-id, and the "type" def id. Loading attributes for both def-ids, which was done in #53721, slowed the compilation of small crates by 2-3%. This PR makes sure we only load the attributes for the "type" def-id, avoiding the slowdown.
-
- 20 9月, 2018 1 次提交
-
-
由 Scott McMurray 提交于
-
- 13 9月, 2018 2 次提交
-
-
由 David Wood 提交于
-
由 F001 提交于
-
- 06 9月, 2018 1 次提交
-
-
由 ms2300 提交于
-
- 02 9月, 2018 1 次提交
-
-
由 Ariel Ben-Yehuda 提交于
This completely splits the IS_NON_EXHAUSTIVE flag. No functional changes intended.
-
- 28 8月, 2018 3 次提交
- 26 8月, 2018 1 次提交
-
-
由 Ariel Ben-Yehuda 提交于
Structs and enums can both be non-exhaustive, with a very different meaning. This PR splits `is_non_exhaustive` to 2 separate functions - 1 for structs, and another for enums, and fixes the places that got the usage confused. Fixes #53549.
-
- 23 8月, 2018 1 次提交
-
-
由 Igor Gutorov 提交于
-
- 22 8月, 2018 5 次提交
- 20 8月, 2018 3 次提交
- 19 8月, 2018 1 次提交
-
-
由 Matthias Krüger 提交于
-
- 10 8月, 2018 2 次提交
-
-
由 Mark Rousskov 提交于
-
由 Mark Rousskov 提交于
-
- 09 8月, 2018 1 次提交
-
-
由 David Wood 提交于
-
- 27 7月, 2018 1 次提交
-
-
由 ljedrz 提交于
-
- 25 7月, 2018 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 24 7月, 2018 1 次提交
-
-
由 Colin Wallace 提交于
-
- 20 7月, 2018 1 次提交
-
-
由 Vadim Petrochenkov 提交于
Use `ptr::eq` for comparing pointers
-
- 18 7月, 2018 3 次提交
-
-
由 Oliver Schneider 提交于
-
由 Oliver Schneider 提交于
-
由 Oliver Schneider 提交于
-
- 16 7月, 2018 1 次提交
-
-
由 csmoe 提交于
-
- 14 7月, 2018 1 次提交
-
-
由 Vadim Petrochenkov 提交于
-
- 08 7月, 2018 1 次提交
-
-
由 Vadim Petrochenkov 提交于
-
- 02 7月, 2018 2 次提交
-
-
由 Niko Matsakis 提交于
Co-authored-by: NTyler Mandry <tmandry@gmail.com>
-
由 Zack M. Davis 提交于
It was pointed out in review that the glob-exported underscore-suffixed convention for `Spanned` HIR nodes is no longer preferred: see February 2016's #31487 for AST's migration away from this style towards properly namespaced NodeKind enums. This concerns #51968.
-
- 01 7月, 2018 1 次提交
-
-
由 Zack M. Davis 提交于
There are at least a couple (and plausibly even three) diagnostics that could use the spans of visibility modifiers in order to be reliably correct (rather than hacking and munging surrounding spans to try to infer where the visibility keyword must have been). We follow the naming convention established by the other `Spanned` HIR nodes: the "outer" type alias gets the "prime" node-type name, the "inner" enum gets the name suffixed with an underscore, and the variant names are prefixed with the prime name and `pub use` exported from here (from HIR). Thanks to veteran reviewer Vadim Petrochenkov for suggesting this uniform approach. (A previous draft, based on the reasoning that `Visibility::Inherited` should not have a span, tried to hack in a named `span` field on `Visibility::Restricted` and a positional field on `Public` and `Crate`. This was ... not so uniform.)
-
- 28 6月, 2018 1 次提交
-
-
由 Oliver Schneider 提交于
-