Florian Diebold f86fe3d891 Don't unify within a reference ... 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.		2019-12-06 15:15:26 +01:00
..
infer	Don't unify within a reference	2019-12-06 15:15:26 +01:00
tests	Don't unify within a reference	2019-12-06 15:15:26 +01:00
traits	Extract built-in trait implementations to separate module	2019-12-03 12:30:50 +01:00
autoderef.rs	Move Ty	2019-11-27 21:16:00 +03:00
db.rs	Add cycle recovery for type aliases	2019-11-30 12:57:32 +01:00
diagnostics.rs	Rename Source -> InFile	2019-11-28 12:50:26 +03:00
display.rs	Move Ty	2019-11-27 21:16:00 +03:00
expr.rs	Replace ra_hir_expand::either with crate	2019-12-03 11:07:56 -05:00
infer.rs	Make unify pub(crate)	2019-12-03 13:58:02 +01:00
lib.rs	Handle cycles in impl types better	2019-11-30 12:57:32 +01:00
lower.rs	Add cycle recovery for type aliases	2019-11-30 12:57:32 +01:00
marks.rs	Move Ty	2019-11-27 21:16:00 +03:00
method_resolution.rs	Fix #2467	2019-12-03 15:01:23 +01:00
op.rs	Move Ty	2019-11-27 21:16:00 +03:00
primitive.rs	Doc primitives	2019-11-26 15:41:48 +03:00
test_db.rs	Fix test compilation	2019-12-04 18:30:42 -05:00
tests.rs	Don't unify within a reference	2019-12-06 15:15:26 +01:00
traits.rs	Extract built-in trait implementations to separate module	2019-12-03 12:30:50 +01:00
utils.rs	Move Ty	2019-11-27 21:16:00 +03:00