aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* account for impls generated by macrosAleksey Kladov2019-09-183-28/+74
|
* Merge #1862bors[bot]2019-09-1719-261/+358
|\ | | | | | | | | | | | | | | 1862: Assoc item resolution refactoring (again) r=flodiebold a=flodiebold This is #1849, with the associated type selection code removed for now. Handling cycles there will need some more thought. Co-authored-by: Florian Diebold <[email protected]>
| * Remove assoc type selection code for now to fix crashesFlorian Diebold2019-09-172-25/+10
| |
| * Add test for `T::Item` cyclesFlorian Diebold2019-09-171-0/+42
| |
| * Remove TraitItem and ImplItem in favor of AssocItemFlorian Diebold2019-09-179-93/+46
| |
| * Small review improvementsFlorian Diebold2019-09-171-5/+3
| |
| * Add test for `<T>::Item`Florian Diebold2019-09-171-10/+22
| |
| * Refactor some moreFlorian Diebold2019-09-174-57/+100
| | | | | | | | | | | | Type-relative paths (`<T>::foo`) also need to work in type context, for example `<T>::Item` is legal. So rather than returning the type ref from the resolver function, just check it before.
| * Refactor associated item resolution moreFlorian Diebold2019-09-172-124/+120
| | | | | | | | | | When resolving an associated item in value namespace, use the `Ty` lowering code for the segments before the last instead of replicating it.
| * Refactor a bit to prepare for resolving trait assoc itemsFlorian Diebold2019-09-1710-52/+83
| |
| * Resolve assoc types on type parametersFlorian Diebold2019-09-172-24/+61
| | | | | | | | | | | | E.g. `fn foo<T: Iterator>() -> T::Item`. It seems that rustc does this only for type parameters and only based on their bounds, so we also only consider traits from bounds.
| * Adapt some testsFlorian Diebold2019-09-171-12/+12
| |
* | Merge #1860bors[bot]2019-09-171-31/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | 1860: remove confusing code r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | remove confusing codeAleksey Kladov2019-09-171-31/+1
| | | | | | | | | | | | | | | | | | I must confess I don't really understand what this code is trying to do, but it definitely misreports changes during fixedpoint iteration, and no tests fail if I remove it, so...
* | | Merge #1859bors[bot]2019-09-171-1/+1
|\| | | |/ |/| | | | | | | | | | | 1859: show error log by default r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * show error log by defaultAleksey Kladov2019-09-171-1/+1
|/
* Merge #1858bors[bot]2019-09-1710-933/+753
|\ | | | | | | | | | | | | | | 1858: use usual token tree for macro expansions r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * use usual token tree for macro expansionAleksey Kladov2019-09-1710-933/+753
| |
* | Merge #1855bors[bot]2019-09-173-418/+448
|\| | | | | | | | | | | | | | | 1855: split mbe expander code into two modules r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * split mbe expander code into two modulesAleksey Kladov2019-09-173-418/+448
|/
* Merge #1817bors[bot]2019-09-1612-148/+235
|\ | | | | | | | | | | | | | | 1817: Support path starting with a type r=matklad a=uHOOCCOOHu The path syntax `<Ty>::foo` Co-authored-by: uHOOCCOOHu <[email protected]>
| * Define known paths and group namesuHOOCCOOHu2019-09-156-49/+63
| |
| * Move store TypeRef of type based path in PathKinduHOOCCOOHu2019-09-154-21/+11
| |
| * Support path starting with a typeuHOOCCOOHu2019-09-1510-128/+211
| |
* | Merge #1852bors[bot]2019-09-162-5/+5
|\ \ | |/ |/| | | | | | | | | | | | | | | 1852: Gracefully handle `const _` items in `ConstData` r=ecstatic-morse a=ecstatic-morse A follow-up to #1847. This makes the `name` field of `ConstData` optional. Co-authored-by: Dylan MacKenzie <[email protected]>
| * Remove `is_unnamed`Dylan MacKenzie2019-09-161-4/+0
| |
| * Gracefully handle `const _` items in `ConstData`Dylan MacKenzie2019-09-162-5/+9
|/
* Merge #1848bors[bot]2019-09-1512-17/+573
|\ | | | | | | | | | | | | | | | | | | | | | | 1848: Parse `..` as a full pattern r=matklad a=ecstatic-morse Resolves #1479. This PR implements [RFC 2707](https://github.com/rust-lang/rfcs/pull/2707) in the parser. It introduces a new `DotDotPat` AST node modeled on `PlaceholderPat` and changes the parsing of tuple and slice patterns to conform to the RFC. Notably, this PR does *not* change the resulting AST when `..` appears in a struct pattern (e.g. `Struct { a, b: c, .. }`). I *think* this is the behavior mandated by RFC 2707, but someone should confirm this. Co-authored-by: Dylan MacKenzie <[email protected]>
| * Generate `dot_dot_test`Dylan MacKenzie2019-09-152-0/+481
| |
| * Bless old tests containing a `..` patternDylan MacKenzie2019-09-155-5/+10
| |
| * Parse `..` as a proper patternDylan MacKenzie2019-09-151-10/+42
| |
| * Add `DotDotPat` to ASTDylan MacKenzie2019-09-154-2/+40
| | | | | | | | This is modeled on `PlaceholderPat`.
* | Merge #1847bors[bot]2019-09-156-40/+90
|\ \ | |/ |/| | | | | | | | | | | 1847: Allow an underscore as the identifier in `const` items r=matklad a=ecstatic-morse [RFC 2526](https://github.com/rust-lang/rust/issues/54912) was recently stabilized, meaning `const _: i32 = 5;` is now a valid item. Co-authored-by: Dylan MacKenzie <[email protected]>
| * Add tests for underscores in `const` and `static` itemsDylan MacKenzie2019-09-153-38/+78
| |
| * Allow an underscore as the identifier in `const` itemsDylan MacKenzie2019-09-153-2/+12
|/
* Merge #1846bors[bot]2019-09-141-1/+1
|\ | | | | | | | | | | | | | | 1846: Remove a dbg! r=flodiebold a=flodiebold Co-authored-by: Florian Diebold <[email protected]>
| * Remove a dbg!Florian Diebold2019-09-141-1/+1
|/
* Merge #1844bors[bot]2019-09-142-12/+11
|\ | | | | | | | | | | | | | | 1844: Support bare `Trait` without dyn r=flodiebold a=flodiebold Co-authored-by: Florian Diebold <[email protected]>
| * Support bare `Trait` without dynFlorian Diebold2019-09-142-12/+11
|/
* Merge #1843bors[bot]2019-09-144-63/+5
|\ | | | | | | | | | | | | | | 1843: Upgrade Chalk r=flodiebold a=flodiebold ... and remove Ty::UnselectedProjection. It'll be handled differently. Co-authored-by: Florian Diebold <[email protected]>
| * Upgrade ChalkFlorian Diebold2019-09-144-63/+5
|/ | | | ... and remove Ty::UnselectedProjection. It'll be handled differently.
* Merge #1838bors[bot]2019-09-135-52/+30
|\ | | | | | | | | | | | | | | 1838: rename add_resolution -> add_scope_def r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * rename add_resolution -> add_scope_defAleksey Kladov2019-09-131-18/+0
| |
| * make PerNs non-genericAleksey Kladov2019-09-134-34/+30
| |
* | Merge #1833bors[bot]2019-09-1313-464/+534
|\| | | | | | | | | | | | | | | 1833: Specify desirable namespace when calling resolve r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * Specify desirable namespace when calling resolveAleksey Kladov2019-09-1313-464/+534
|/ | | | That way, we are able to get rid of a number of unreachable statements
* Merge #1835bors[bot]2019-09-1221-141/+135
|\ | | | | | | | | | | | | | | 1835: rename AdtDef -> Adt r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * rename AdtDef -> AdtAleksey Kladov2019-09-1220-99/+90
| |
| * generalize impl_froms to nested enumsAleksey Kladov2019-09-124-58/+26
| |
| * make various enums "inherit" from AdtDefAleksey Kladov2019-09-1217-121/+156
|/
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 13:28:51 +0000