Skip to content

Register wf obligation before normalizing in wfcheck #100046

Closed
compiler-errors wants to merge 1 commit intorust-lang:masterfrom
compiler-errors:dont-normalize-in-wfcheck
Closed

Register wf obligation before normalizing in wfcheck #100046
compiler-errors wants to merge 1 commit intorust-lang:masterfrom
compiler-errors:dont-normalize-in-wfcheck

Conversation

@compiler-errors
Copy link
Copy Markdown
Contributor

@compiler-errors compiler-errors commented Aug 2, 2022

Fixes #100041.

Why are we normalizing in wfcheck at all? Should we just be dealing w unnormalized types? I guess whether we normalize or not at all has effects on implied bounds...

cc @rust-lang/types

r? types

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. finished-final-comment-period The final comment period is finished for this PR / Issue. S-blocked Status: Blocked on something else such as an RFC or other implementation work. T-types Relevant to the types team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Normalization can skip WF