Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Refactor associated method resolution a bit and make it work with generics | Florian Diebold | 2019-02-23 | 1 | -4/+4 |
| | |||||
* | Merge #866 | bors[bot] | 2019-02-22 | 5 | -0/+89 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | 866: Implement basic support for Associated Methods r=flodiebold a=vipentti This is my attempt at learning to understand how the type inference works by adding basic support for associated methods. Currently it does not resolve associated types or constants. The basic idea is that `Resolver::resolve_path` returns a new `PathResult` type, which has two variants, `FullyResolved` and `PartiallyResolved`, fully resolved matches the previous behavior, where as `PartiallyResolved` contains the `PerNs<Resolution` in addition to a `segment_index` which contains the index of the segment which we failed to resolve. This index can then be used to continue inference in `infer_path_expr` using the `Type` we managed to resolve. This changes some of the previous apis, so looking for feedback and suggestions. This should enable fixing #832 Co-authored-by: Ville Penttinen <[email protected]> | ||||
| * | Remove Const inference for now, refactor PathResult | Ville Penttinen | 2019-02-21 | 1 | -7/+7 |
| | | |||||
| * | Implement basic support for Associated Methods and Constants | Ville Penttinen | 2019-02-21 | 5 | -0/+89 |
| | | | | | | | | | | | | | | This is done in `infer_path_expr`. When `Resolver::resolve_path` returns `PartiallyResolved`, we use the returned `Resolution` together with the given `segment_index` to check if we can find something matching the segment at segment_index in the impls for that particular type. | ||||
* | | Fix handling of generics in tuple variants and refactor a bit | Florian Diebold | 2019-02-20 | 2 | -3/+26 |
|/ | | | | | | Also make them display a tiny bit nicer. Fixes #860. | ||||
* | Merge #852 | bors[bot] | 2019-02-18 | 1 | -34/+38 |
|\ | | | | | | | | | | | | | | | 852: Handle != r=flodiebold a=matklad r? @flodiebold Co-authored-by: Aleksey Kladov <[email protected]> | ||||
| * | handle != operator | Aleksey Kladov | 2019-02-18 | 1 | -34/+38 |
| | | |||||
* | | Handle tuple structs / enum variants properly in type inference | Florian Diebold | 2019-02-17 | 1 | -9/+9 |
|/ | |||||
* | Unify with the autorefed/autoderefed receiver type during method resolution | Florian Diebold | 2019-02-17 | 1 | -0/+16 |
| | |||||
* | Handle generic args for method calls | Florian Diebold | 2019-02-16 | 1 | -3/+3 |
| | |||||
* | Handle impl generics in method calls | Florian Diebold | 2019-02-16 | 2 | -47/+47 |
| | |||||
* | Add a test for impl generics | Florian Diebold | 2019-02-16 | 1 | -0/+39 |
| | |||||
* | Fix another crash | Florian Diebold | 2019-02-12 | 1 | -0/+12 |
| | |||||
* | Fix another crash, and try harder to prevent stack overflows | Florian Diebold | 2019-02-09 | 1 | -0/+30 |
| | |||||
* | Fix another crash found when analyzing rustc | Florian Diebold | 2019-02-09 | 1 | -0/+16 |
| | |||||
* | Fix handling of literal patterns | Florian Diebold | 2019-02-09 | 1 | -0/+13 |
| | | | | | Wrap them in a LiteralPat node so they can be distinguished from literal expressions. | ||||
* | Fix two crashes found by running inference on all of rustc | Florian Diebold | 2019-02-09 | 2 | -0/+27 |
| | |||||
* | Test more Self inference | kjeremy | 2019-02-04 | 1 | -3/+7 |
| | |||||
* | Use new Resolver API in type inference | Florian Diebold | 2019-02-01 | 3 | -15/+15 |
| | |||||
* | Merge #701 | bors[bot] | 2019-01-30 | 2 | -14/+23 |
|\ | | | | | | | | | | | | | | | | | | | 701: Minor type inference tweaks r=flodiebold a=marcusklaas Pass down expectation for reference expressions and type the guard in match expressions. I wasn't able to add a test for the former addition because the type variable previously introduced would always resolve to the right type in the things I tried! Co-authored-by: Marcus Klaas de Vries <[email protected]> | ||||
| * | Add test for passing on ref expectations | Marcus Klaas de Vries | 2019-01-30 | 1 | -4/+10 |
| | | |||||
| * | Infer type of match guard | Marcus Klaas de Vries | 2019-01-28 | 1 | -10/+13 |
| | | |||||
* | | Added support for primitive types type inference when using std::ops::Not | WizardOfMenlo | 2019-01-28 | 1 | -12/+25 |
| | | |||||
* | | Process second review | Marcus Klaas de Vries | 2019-01-27 | 1 | -5/+5 |
| | | |||||
* | | Use type information from the turbofish | Marcus Klaas de Vries | 2019-01-27 | 2 | -6/+9 |
| | | |||||
* | | Add a FnSig to Ty::FnDef | Marcus Klaas de Vries | 2019-01-27 | 6 | -30/+30 |
| | | |||||
* | | Add missing ty test snapshot | Marcus Klaas de Vries | 2019-01-27 | 1 | -0/+23 |
| | | |||||
* | | Add type params to FnSignature | Marcus Klaas de Vries | 2019-01-27 | 5 | -54/+54 |
|/ | |||||
* | Handle cycles in type vars | Florian Diebold | 2019-01-26 | 2 | -0/+35 |
| | | | | This might be the cause of #587. | ||||
* | fix AST for if expressions | Aleksey Kladov | 2019-01-26 | 1 | -0/+17 |
| | | | | then is not always a block... | ||||
* | Fix type inference of binops on int/float variables | Florian Diebold | 2019-01-25 | 1 | -0/+13 |
| | | | | Fixes #651. | ||||
* | new struct id | Aleksey Kladov | 2019-01-24 | 1 | -6/+6 |
| | |||||
* | Update snaps | Jeremy A. Kolb | 2019-01-22 | 24 | -96/+144 |
| | |||||
* | Use insta for ty tests | Florian Diebold | 2019-01-21 | 24 | -0/+605 |