rust/crates/ra_hir/src/ty/tests/data/0004_struct.txt

[86; 90) 'C(1)': [unknown]
[121; 122) 'B': B
[86; 87) 'C': [unknown]
[129; 130) '1': [unknown]
[107; 108) 'a': A
[127; 128) 'C': [unknown]
[139; 142) 'a.b': B
[114; 133) 'A { b:...C(1) }': A
[148; 151) 'a.c': C
[148; 149) 'a': A
[139; 140) 'a': A
[72; 154) '{     ...a.c; }': ()
[96; 97) 'B': [unknown]
[88; 89) '1': [unknown]
[82; 83) 'c': [unknown]
[127; 131) 'C(1)': C
Add basic HIR and types for structs/enums 2018-12-24 19:07:48 +01:00			`[86; 90) 'C(1)': [unknown]`
Implement type variables This will really become necessary when we implement generics, but even now, it allows us to reason 'backwards' to infer types of expressions that we didn't understand for some reason. We use ena, the union-find implementation extracted from rustc, to keep track of type variables. 2018-12-26 17:00:42 +01:00			`[121; 122) 'B': B`
Do name resolution by namespace (types/values) 2018-12-24 20:32:39 +01:00			`[86; 87) 'C': [unknown]`
Infer result of struct literals, and recurse into their child expressions 2018-12-24 21:00:14 +01:00			`[129; 130) '1': [unknown]`
Add basic HIR and types for structs/enums 2018-12-24 19:07:48 +01:00			`[107; 108) 'a': A`
Infer result of struct literals, and recurse into their child expressions 2018-12-24 21:00:14 +01:00			`[127; 128) 'C': [unknown]`
Type field accesses 2018-12-25 13:54:38 +01:00			`[139; 142) 'a.b': B`
Infer result of struct literals, and recurse into their child expressions 2018-12-24 21:00:14 +01:00			`[114; 133) 'A { b:...C(1) }': A`
Type field accesses 2018-12-25 13:54:38 +01:00			`[148; 151) 'a.c': C`
			`[148; 149) 'a': A`
			`[139; 140) 'a': A`
Infer result of struct literals, and recurse into their child expressions 2018-12-24 21:00:14 +01:00			`[72; 154) '{ ...a.c; }': ()`
Do name resolution by namespace (types/values) 2018-12-24 20:32:39 +01:00			`[96; 97) 'B': [unknown]`
Add basic HIR and types for structs/enums 2018-12-24 19:07:48 +01:00			`[88; 89) '1': [unknown]`
			`[82; 83) 'c': [unknown]`
Implement type variables This will really become necessary when we implement generics, but even now, it allows us to reason 'backwards' to infer types of expressions that we didn't understand for some reason. We use ena, the union-find implementation extracted from rustc, to keep track of type variables. 2018-12-26 17:00:42 +01:00			`[127; 131) 'C(1)': C`