Skip to content

Move classType checks for new expressions to PostTyper #11788

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

Merged
merged 2 commits into from
Mar 17, 2021

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Mar 17, 2021

When typechecking a new expression, we cannot reliably tell what the actual underlying
type is since this might depend on type inference that still has to happen at this point.

Fixes #11781

odersky added 2 commits March 17, 2021 12:20
When typechecking a new expression, we cannot reliably tell what the actual underlying
type is since this might depend on type inference that still has to happen at this point.
Copy link
Contributor

@liufengyun liufengyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@liufengyun liufengyun merged commit f267f91 into scala:master Mar 17, 2021
@liufengyun liufengyun deleted the fix-11781 branch March 17, 2021 13:35
@Kordyjan Kordyjan added this to the 3.0.0 milestone Aug 2, 2023
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

Successfully merging this pull request may close these issues.

Regression: new <type alias> should compile
3 participants