You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to handle normalization in chalk and ideas about what a generic
6
+
library to represent types might look like.
7
+
8
+
## summary
9
+
10
+
Key points in the discussion:
11
+
12
+
*[how does normalization work in chalk today](https://rust-lang.zulipchat.com/#narrow/stream/144729-wg-traits/topic/meeting.202019-10-16/near/178314511)
13
+
*[would like to remove unnormalized projections and move that logic to clause lowering](https://rust-lang.zulipchat.com/#narrow/stream/144729-wg-traits/topic/meeting.202019-10-16/near/178315108)
14
+
*[but this makes lowering more complex](https://rust-lang.zulipchat.com/#narrow/stream/144729-wg-traits/topic/meeting.202019-10-16/near/178315630)
15
+
*[can use generics to keep things straight](https://rust-lang.zulipchat.com/#narrow/stream/144729-wg-traits/topic/meeting.202019-10-16/near/178315802)
16
+
*[and in particular a typefamily trait](https://rust-lang.zulipchat.com/#narrow/stream/144729-wg-traits/topic/meeting.202019-10-16/near/178316023)
17
+
*[this typefamily trait can be the foundation for a generic type library](https://rust-lang.zulipchat.com/#narrow/stream/144729-wg-traits/topic/meeting.202019-10-16/near/178316849)
0 commit comments