Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we be eagerly evaluating consts in the "old"-style normalizer? #28

Open
compiler-errors opened this issue Jun 1, 2023 · 0 comments

Comments

@compiler-errors
Copy link
Member

compiler-errors commented Jun 1, 2023

Right now, the AssocTypeFolder will eagerly evaluate consts unless GCE is enabled. We still have usages of this folder (the "old"-style normalizer) all over the place, and tearing that out is a lot of work.

Eventually, I'd like to move away from normalizing types or consts unless there's a clear reason for the normalization (i.e. we structurally normalize types in HIR typeck for various reasons like field acceses).

Right now we continue to eagerly normalize types in HIR typeck. Doing this for consts and not for types does introduce an incongruency that may make subtle alias-relate bugs appear just for consts, but it does get us one step closer to always-lazy-norm...

rust-lang/rust#112183 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant