| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | internal: add fn to minicore | Aleksey Kladov | 2021-06-16 | 1 | -40/+36 |
| | | |||||
| * | Fix coercion in match with expected type | Florian Diebold | 2021-06-12 | 1 | -40/+17 |
| | | | | | Plus add infrastructure to test type mismatches without expect. | ||||
| * | Fix bind patterns always being treated as ref taking patterns | Lukas Wirth | 2021-06-02 | 1 | -19/+28 |
| | | |||||
| * | Fix test after rebase | Florian Diebold | 2021-05-21 | 1 | -1/+1 |
| | | |||||
| * | internal: Record mismatches of pattern types. | Dawer | 2021-05-19 | 1 | -1/+57 |
| | | |||||
| * | Merge #8813 | bors[bot] | 2021-05-16 | 1 | -4/+4 |
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8813: Get some more array lengths! r=lf- a=lf- This is built on #8799 and thus contains its changes. I'll rebase it onto master when that one gets merged. It adds support for r-a understanding the length of: * `let a: [u8; 2] = ...` * `let a = b"aaa"` * `let a = [0u8; 4]` I have added support for getting the values of byte strings, which was not previously there. I am least confident in the correctness of this part and it probably needs some more tests, as we currently have only one test that exercised that part (!). Fixes #2922. Co-authored-by: Jade <[email protected]> | ||||
| | * | Add lowering of array lengths in types | Jade | 2021-05-13 | 1 | -4/+4 |
| | | | | | | | | | | | | | | | | | | | | | | | Now e.g. ```rust fn a(b: [u8; 2]) { } ``` will know about the length of b. | ||||
| * | | Fix false positive "Missing match arm". | Dawer | 2021-05-14 | 1 | -1/+1 |
| |/ | |||||
| * | Add basic support for array lengths in types | Jade | 2021-05-11 | 1 | -3/+3 |
| | | | | | | | | | | | This recognizes `let a = [1u8, 2, 3]` as having type `[u8; 3]` instead of the previous `[u8; _]`. Byte strings and `[0u8; 2]` kinds of range array declarations are unsupported as before. I don't know why a bunch of our rustc tests had single quotes inside strings un-escaped by `UPDATE_EXPECT=1 cargo t`, but I don't think it's bad? Maybe something in a nightly? | ||||
| * | Support macros in pattern position | Jonas Schievink | 2021-04-11 | 1 | -1/+27 |
| | | |||||
| * | Fix box pattern inference panic | Lukas Wirth | 2021-03-21 | 1 | -0/+22 |
| | | |||||
| * | Use upstream cov-mark | Laurențiu Nicola | 2021-03-08 | 1 | -2/+1 |
| | | |||||
| * | Implement const pat inference | Lukas Wirth | 2020-12-23 | 1 | -0/+30 |
| | | |||||
| * | Properly infer tuple struct patterns when encountering ellipsis | Lukas Wirth | 2020-11-24 | 1 | -0/+48 |
| | | |||||
| * | Properly infer tuple patterns when encountering ellipsis | Lukas Wirth | 2020-11-24 | 1 | -0/+47 |
| | | |||||
| * | Add box pattern test | Jonas Schievink | 2020-09-12 | 1 | -0/+25 |
| | | |||||
| * | Switch to expect_test from crates.io | Aleksey Kladov | 2020-08-21 | 1 | -1/+1 |
| | | |||||
| * | Rename ra_hir_ty -> hir_ty | Aleksey Kladov | 2020-08-13 | 1 | -0/+656 |
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |