Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | | Added test for check doc strings in crates. | Alexander Andreev | 2019-09-30 | 27 | -9/+59 | |
|/ | | | | #1856 | |||||
* | Merge #1815 | bors[bot] | 2019-09-27 | 17 | -124/+361 | |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1815: Support correct `$crate` expansion in macros r=uHOOCCOOHu a=uHOOCCOOHu This PR makes normal use cases of `$crate` from macros work as expected. It makes more macros from `std` work. Type inference works well with `panic`, `unimplemented`, `format`, and maybe more. Sadly that `vec![1, 2, 3]` still not works, but it is not longer an issue about macro. Screenshot: ![Screenshot_20190927_022136](https://user-images.githubusercontent.com/14816024/65714465-b4568f80-e0cd-11e9-8043-dd44c2ae8040.png) Co-authored-by: uHOOCCOOHu <[email protected]> | |||||
| * | Fix | uHOOCCOOHu | 2019-09-27 | 2 | -2/+2 | |
| | | ||||||
| * | Support `$crate` in item and expr place. | uHOOCCOOHu | 2019-09-26 | 12 | -35/+266 | |
| | | ||||||
| * | Store crate info in `MacroDefId` | uHOOCCOOHu | 2019-09-26 | 3 | -5/+11 | |
| | | ||||||
| * | Refactor `Name` ready for hygienic macro | uHOOCCOOHu | 2019-09-26 | 3 | -84/+84 | |
| | | ||||||
* | | Add SubstsBuilder | Florian Diebold | 2019-09-26 | 11 | -126/+212 | |
|/ | | | | + further refactoring. | |||||
* | Support all coercion places | uHOOCCOOHu | 2019-09-25 | 3 | -96/+216 | |
| | ||||||
* | Support custom `CoerceUnsized` | uHOOCCOOHu | 2019-09-25 | 4 | -247/+476 | |
| | | | | Split out tests about coercion | |||||
* | Better handle never type and branch merging | uHOOCCOOHu | 2019-09-25 | 5 | -181/+392 | |
| | | | | Split out tests for never type to another file | |||||
* | Support basic implicit type coerce | uHOOCCOOHu | 2019-09-25 | 2 | -142/+383 | |
| | ||||||
* | Support auto-deref in argument position | uHOOCCOOHu | 2019-09-25 | 2 | -1/+161 | |
| | ||||||
* | Resolve trait associated items | Florian Diebold | 2019-09-25 | 5 | -19/+78 | |
| | | | | E.g. `Default::default` or `<Foo as Default>::default`. | |||||
* | Fix retrieval of the Fn traits | Florian Diebold | 2019-09-25 | 3 | -7/+6 | |
| | | | | | I used the wrong query, so it only used the lang items from the respective crate... | |||||
* | Merge #1906 | bors[bot] | 2019-09-25 | 1 | -2/+5 | |
|\ | | | | | | | | | | | | | | | 1906: Add missing lang-items to `def_crates` r=matklad a=sinkuu Co-authored-by: Shotaro Yamada <[email protected]> | |||||
| * | Add missing lang-items to `def_crates` | Shotaro Yamada | 2019-09-25 | 1 | -2/+5 | |
| | | ||||||
* | | Remove redundant clone() | Shotaro Yamada | 2019-09-25 | 8 | -22/+14 | |
| | | ||||||
* | | Avoid intermediate allocation | Shotaro Yamada | 2019-09-25 | 1 | -1/+1 | |
|/ | ||||||
* | Implement the call argument checking order hack for closures | Florian Diebold | 2019-09-24 | 3 | -12/+108 | |
| | ||||||
* | Make the closure_1 test work | Florian Diebold | 2019-09-24 | 3 | -27/+40 | |
| | ||||||
* | Make closures impl closure traits | Florian Diebold | 2019-09-24 | 4 | -41/+188 | |
| | ||||||
* | Give closures types | Florian Diebold | 2019-09-24 | 5 | -21/+78 | |
| | ||||||
* | Upgrade Chalk again | Florian Diebold | 2019-09-24 | 1 | -3/+6 | |
| | ||||||
* | Merge #1898 | bors[bot] | 2019-09-23 | 2 | -2/+2 | |
|\ | | | | | | | | | | | | | | | | | 1898: Drive by lints r=kjeremy a=kjeremy Co-authored-by: kjeremy <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]> | |||||
| * | Drive by lints | kjeremy | 2019-09-23 | 2 | -2/+2 | |
| | | ||||||
* | | Upgrade Chalk | Florian Diebold | 2019-09-23 | 1 | -4/+6 | |
|/ | ||||||
* | Split off path expression inference code into submodule | Florian Diebold | 2019-09-23 | 2 | -172/+199 | |
| | ||||||
* | Handle projection types from Chalk | Florian Diebold | 2019-09-22 | 1 | -1/+5 | |
| | ||||||
* | Handle associated type shorthand (`T::Item`) | Florian Diebold | 2019-09-22 | 6 | -22/+168 | |
| | | | | | | | | | | | | This is only allowed for generic parameters (including `Self` in traits), and special care needs to be taken to not run into cycles while resolving it, because we use the where clauses of the generic parameter to find candidates for the trait containing the associated type, but the where clauses may themselves contain instances of short-hand associated types. In some cases this is even fine, e.g. we might have `T: Trait<U::Item>, U: Iterator`. If there is a cycle, we'll currently panic, which isn't great, but better than overflowing the stack... | |||||
* | fix module attr path | gfreezy | 2019-09-20 | 3 | -2/+40 | |
| | ||||||
* | introduce FromSource trait | Ekaterina Babshukova | 2019-09-19 | 6 | -111/+247 | |
| | ||||||
* | account for impls generated by macros | Aleksey Kladov | 2019-09-18 | 3 | -28/+74 | |
| | ||||||
* | Merge #1862 | bors[bot] | 2019-09-17 | 12 | -242/+336 | |
|\ | | | | | | | | | | | | | | | 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 crashes | Florian Diebold | 2019-09-17 | 2 | -25/+10 | |
| | | ||||||
| * | Add test for `T::Item` cycles | Florian Diebold | 2019-09-17 | 1 | -0/+42 | |
| | | ||||||
| * | Remove TraitItem and ImplItem in favor of AssocItem | Florian Diebold | 2019-09-17 | 7 | -88/+41 | |
| | | ||||||
| * | Small review improvements | Florian Diebold | 2019-09-17 | 1 | -5/+3 | |
| | | ||||||
| * | Add test for `<T>::Item` | Florian Diebold | 2019-09-17 | 1 | -10/+22 | |
| | | ||||||
| * | Refactor some more | Florian Diebold | 2019-09-17 | 4 | -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 more | Florian Diebold | 2019-09-17 | 2 | -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 items | Florian Diebold | 2019-09-17 | 5 | -38/+66 | |
| | | ||||||
| * | Resolve assoc types on type parameters | Florian Diebold | 2019-09-17 | 2 | -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 tests | Florian Diebold | 2019-09-17 | 1 | -12/+12 | |
| | | ||||||
* | | remove confusing code | Aleksey Kladov | 2019-09-17 | 1 | -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 #1817 | bors[bot] | 2019-09-16 | 9 | -144/+227 | |
|\ | | | | | | | | | | | | | | | 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 names | uHOOCCOOHu | 2019-09-15 | 6 | -49/+63 | |
| | | ||||||
| * | Move store TypeRef of type based path in PathKind | uHOOCCOOHu | 2019-09-15 | 3 | -20/+10 | |
| | | ||||||
| * | Support path starting with a type | uHOOCCOOHu | 2019-09-15 | 7 | -124/+203 | |
| | | ||||||
* | | Remove `is_unnamed` | Dylan MacKenzie | 2019-09-16 | 1 | -4/+0 | |
| | | ||||||
* | | Gracefully handle `const _` items in `ConstData` | Dylan MacKenzie | 2019-09-16 | 2 | -5/+9 | |
|/ |