Skip to content

bugfix: Check for error before checking members of product type in getUnapplySelectors #23358

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 3 commits into from
Jun 16, 2025

Conversation

aherlihy
Copy link
Contributor

Fixes #23156

I'm not 100% sure this is the best way to check for error types, so would appreciate any guidance!

Copy link
Contributor

@EugeneFlesselle EugeneFlesselle left a comment

Choose a reason for hiding this comment

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

It looks liks we're diverging in Applications.productSelectorTypes, so I think we should move the check there in case a similar problem occurs coming from some other path.
Otherwise this seems like the correct way to check for ErrorTypes AFAIK 👍

@aherlihy
Copy link
Contributor Author

@EugeneFlesselle if it looks good, will you approve the PR so it can be merged before the deadline? Thank you!

@aherlihy aherlihy merged commit 83e9c14 into scala:main Jun 16, 2025
29 checks passed
@aherlihy aherlihy deleted the i23156 branch June 16, 2025 09:22
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.

Compiler goes OOM/infinite loop after unknown type in extractor
2 participants