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

Investigate why the Block TypeAssigner avoids types but not terms #2987

Open
smarter opened this issue Aug 16, 2017 · 3 comments
Open

Investigate why the Block TypeAssigner avoids types but not terms #2987

smarter opened this issue Aug 16, 2017 · 3 comments

Comments

@smarter
Copy link
Member

smarter commented Aug 16, 2017

See e7e643c and the follow-up discussion at #2945 (comment). Ever TypeAssigner needs to be changed to avoid everything or we need to document why there's a special case.

@dwijnand
Copy link
Member

@smarter Is this still true and need doing? I'm thinking of looking at it myself with Seth.

@smarter
Copy link
Member Author

smarter commented Jan 11, 2022

No idea. I forgot the context here, but long term I think we should see if we can get rid of TypeOps#avoid in favor of LevelAvoidMap as I outlined in https://github.com/lampepfl/dotty/blob/1292246c9646db12391cb7e42ce951722ac7fd03/compiler/src/dotty/tools/dotc/core/TypeOps.scala#L494-L498 which came out of #14026

@dwijnand dwijnand self-assigned this Jan 11, 2022
@dwijnand dwijnand removed their assignment Feb 23, 2022
@odersky
Copy link
Contributor

odersky commented Apr 5, 2022

@smarter Feel free to close if you think this is addressed now.

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

No branches or pull requests

3 participants