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

Avoid creation of @SplicedType quote local refrences #17051

Merged
merged 1 commit into from
Mar 15, 2023

Conversation

nicolasstucki
Copy link
Contributor

The type declarations annotated with @SplicedType are only meant for types that come from outside the quote. If the reference to the Type[T] is to a definition within the quote (i.e. its level is grater than 0) we can use it directly. The @SplicedType for that type will be generated in a future compilation phase when the Type[T] definition reaches level 0.

Fixes #17026

@nicolasstucki nicolasstucki marked this pull request as ready for review March 7, 2023 08:22
@nicolasstucki nicolasstucki requested a review from smarter March 7, 2023 08:22
@nicolasstucki nicolasstucki requested review from natsukagami and removed request for smarter March 11, 2023 07:15
@nicolasstucki nicolasstucki assigned natsukagami and unassigned smarter Mar 11, 2023
The type declarations annotated with `@SplicedType` are only meant for
types that come from outside the quote. If the reference to the `Type[T]`
is to a definition within the quote (i.e. its level is grater than 0) we
can use it directly. The `@SplicedType` for that type will be generated
in a future compilation phase when the `Type[T]` definition reaches
level 0.

Fixes scala#17026
Copy link
Contributor

@natsukagami natsukagami left a comment

Choose a reason for hiding this comment

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

Maybe tests need to be re-run

@nicolasstucki nicolasstucki enabled auto-merge March 15, 2023 10:09
@nicolasstucki nicolasstucki merged commit b625340 into scala:main Mar 15, 2023
@nicolasstucki nicolasstucki deleted the fix-17026 branch March 15, 2023 11:16
@Kordyjan Kordyjan added this to the 3.3.1 milestone Aug 1, 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.

"Could not find proxy for implicit evidence" when using doubly nested quotes
4 participants