aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_ty/src/tests/coercion.rs
Commit message (Collapse)AuthorAgeFilesLines
* Minor test fixes / new testsFlorian Diebold2021-05-251-15/+62
|
* Fix type mismatch caused by macrosFlorian Diebold2021-05-251-0/+44
| | | | | | MacroStmts should be completely transparent, but it prevented coercion. (I should maybe give `infer_expr` and `infer_expr_inner` better names.)
* Fix handling of diverging branches in match coercionFlorian Diebold2021-05-211-0/+39
| | | | Fixes #7626.
* Fix coercion of two closures to a function pointerFlorian Diebold2021-05-211-1/+16
| | | | Fixes #8604.
* Add support for lengths in array repeats, if they are literalsJade2021-05-131-1/+1
| | | | Now we will get the type of `[0u8; 4]`.
* Add lowering of array lengths in typesJade2021-05-131-22/+22
| | | | | | | | | | | Now e.g. ```rust fn a(b: [u8; 2]) { } ``` will know about the length of b.
* Add basic support for array lengths in typesJade2021-05-111-45/+45
| | | | | | | | | | 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?
* Use upstream cov-markLaurențiu Nicola2021-03-081-3/+2
|
* Switch to expect_test from crates.ioAleksey Kladov2020-08-211-1/+1
|
* Rename ra_hir_ty -> hir_tyAleksey Kladov2020-08-131-0/+861