Refactor: extract macro runtime classes to shared files#614
Merged
TimvdLippe merged 1 commit intoFeb 20, 2026
Merged
Conversation
Contributor
Author
|
@TimvdLippe next step is ready for your review. Thanks! |
TimvdLippe
approved these changes
Feb 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Another baby step toward Scala 3
Move runtime classes out of macro-only files into shared *Runtime files, preparing for Scala 2/3 macro source split.
*Runtime classes have no macro code thus can be reused by any Scala version. WhenMacro/VerifyMacro retain all macro code, type aliases and val re-exports for backward compatibility. Quasiquotes updated to reference *Runtime types directly.