Correctly handle backticked macro keyword in Scala 3 #163
Conversation
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
Member
|
Thanks @KacperFKorban ! Can send me an email with international bank transfer detail to [email protected] and I'll close out the bounty |
Contributor
Author
|
Hi, that's fine. I don't really care about the bounty, I was just looking for a Scala 3 issue in a cool codebase. |
Member
|
@KacperFKorban No worries! In that case I'll pass the bounty to the Scala Center as a donation to support their good works. |
lihaoyi
pushed a commit
to com-lihaoyi/scalasql
that referenced
this pull request
Oct 20, 2025
with scala 3. citing Sourcecode release notes: > 0.4.2 > Fix NullPointerException when using sourcecode.File in Scala 3 repl (com-lihaoyi/sourcecode#161) > Correctly handle backticked macro keyword in Scala 3 (com-lihaoyi/sourcecode#163)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Change the synthetic check to use flags and exposed methods instead of names.
#120