Skip to content

Improve type test error message position #12255

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 1 commit into from
Apr 28, 2021

Conversation

nicolasstucki
Copy link
Contributor

This will help with the siuation found in #12253

This will help with the siuation found in scala#12253
@nicolasstucki nicolasstucki marked this pull request as draft April 28, 2021 11:21
@nicolasstucki nicolasstucki linked an issue Apr 28, 2021 that may be closed by this pull request
@nicolasstucki nicolasstucki marked this pull request as ready for review April 28, 2021 12:33
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

-- Error: tests/neg-custom-args/fatal-warnings/i12253.scala:11:38 ------------------------------------------------------
11 | case extractors.InlinedLambda(_, Select(_, name)) => Expr(name) // error // error
| ^
| the type test for q1.reflect.Select cannot be checked at runtime
Copy link
Contributor

Choose a reason for hiding this comment

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

For future consideration: Maybe it's better for the unapplys to take a less specific type to avoid such warnings.

@nicolasstucki nicolasstucki enabled auto-merge April 28, 2021 12:57
@nicolasstucki nicolasstucki merged commit b1a3e6d into scala:master Apr 28, 2021
@nicolasstucki nicolasstucki deleted the fix-#12253-2 branch April 28, 2021 13:13
@Kordyjan Kordyjan added this to the 3.0.1 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.

Possible bug in tasty reflection regarding matching of trees
3 participants