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

Backport "Fix isAliasType" to LTS #21081

Merged
merged 5 commits into from
Jul 6, 2024
Merged

Backport "Fix isAliasType" to LTS #21081

merged 5 commits into from
Jul 6, 2024

Conversation

WojciechMazur
Copy link
Contributor

Backports #20195 to the LTS branch.

PR submitted by the release tooling.
[skip ci]

odersky and others added 5 commits July 6, 2024 12:28
Symbols that had the TypeParam flag set were classified as alias types unless they also had
the Deferred flag set. Maybe this did not break that much since Namer always added the Deferred
for type parameters. But export forwarders use synthesized parameters which did not have Deferred
set.

[Cherry-picked 7e1c4ca]
There were some other occurrences of isAbstractType where it was not clear why
type parameters should be excluded. Use isAbstractOrParamType as the new default.

[Cherry-picked 413c667]
Always use isAbstractorParamType. quotes.reflect still uses isAbstractType for backwards compatibility,
but it now also includes type parameters. This was the case anyway before for type parameters set up by
Namer.

[Cherry-picked aaacc43]
Base automatically changed from lts-20137 to lts-3.3 July 6, 2024 14:02
@WojciechMazur
Copy link
Contributor Author

No regressions detected in the community build up to lts-20173.

Reference

@WojciechMazur WojciechMazur merged commit e6592d9 into lts-3.3 Jul 6, 2024
19 checks passed
@WojciechMazur WojciechMazur deleted the lts-20195 branch July 6, 2024 14:02
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.

2 participants