GitHub / rust-lang/trait-system-refactor-initiative issues and pull requests
Labelled with: not-blocking-coherence
#61 - Outlives obligations aren't normalized before processing
Issue -
State: closed - Opened by compiler-errors over 2 years ago
- 2 comments
Labels: A-normalization, not-blocking-coherence
#59 - Unsound associated type outlives bound due to lazy norm
Issue -
State: open - Opened by compiler-errors over 2 years ago
- 1 comment
Labels: not-blocking-coherence
#23 - hir typeck decision making now checks whether nested `eq`/`sub` obligations hold
Issue -
State: open - Opened by lcnr over 2 years ago
- 1 comment
Labels: not-blocking-coherence
#17 - should looking up the defined opaque types be structural or semantic
Issue -
State: closed - Opened by lcnr over 2 years ago
- 2 comments
Labels: not-blocking-coherence
#16 - defining opaque types with aliases which normalize to params
Issue -
State: closed - Opened by lcnr over 2 years ago
- 1 comment
Labels: not-blocking-coherence
#15 - structurally resolve how does it work
Issue -
State: open - Opened by lcnr over 2 years ago
Labels: not-blocking-coherence
#12 - normalization does not use impls covered by param env candidates
Issue -
State: open - Opened by lcnr over 2 years ago
- 5 comments
Labels: S-increased-expressiveness, A-normalization, not-blocking-coherence
#3 - Should we deeply normalize during writeback, or at the post-typeck places that need a "structurally resolved" type?
Issue -
State: closed - Opened by compiler-errors over 2 years ago
- 3 comments
Labels: A-normalization, not-blocking-coherence