| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Fix coercion of &T to itself | Florian Diebold | 2020-02-16 | 1 | -0/+22 |
| | | | | | | The autoderef coercion logic did not handle matching placeholders. This led to some type mismatches. | ||||
| * | Fix printing of function types | Florian Diebold | 2020-02-07 | 1 | -13/+13 |
| | | |||||
| * | Standard formatting for array types | Aleksey Kladov | 2020-01-28 | 1 | -48/+48 |
| | | |||||
| * | Coerce closures to fn pointers | Florian Diebold | 2019-12-20 | 1 | -0/+39 |
| | | | | | E.g. `let x: fn(A) -> B = |x| { y };` | ||||
| * | Fix coercion of last expression in function body | Florian Diebold | 2019-12-20 | 1 | -0/+16 |
| | | |||||
| * | Handle closure return types | Florian Diebold | 2019-12-20 | 1 | -0/+31 |
| | | | | | Fixes #2547. | ||||
| * | Fix coercion from &Foo to an inference variable in a reference | Florian Diebold | 2019-12-08 | 1 | -0/+37 |
| | | | | | We didn't try to unify within the reference, but we should. | ||||
| * | Don't unify within a reference | Florian Diebold | 2019-12-06 | 1 | -0/+36 |
| | | | | | | | | If we are expecting a `&Foo` and get a `&something`, when checking the `something`, we are *expecting* a `Foo`, but we shouldn't try to unify whatever we get with that expectation, because it could actually be a `&Foo`, and `&&Foo` coerces to `&Foo`. So this fixes quite a few false type mismatches. | ||||
| * | Move Ty | Aleksey Kladov | 2019-11-27 | 1 | -0/+369 |
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |