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

expose & fix scalameta deprecations WIP #1744

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

bjaglin
Copy link
Collaborator

@bjaglin bjaglin commented Mar 20, 2023

No description provided.

@bjaglin bjaglin changed the title expose & fix scalameta deprecations expose & fix scalameta deprecations WIP Mar 20, 2023
@bjaglin bjaglin force-pushed the scalameta-deprecations branch from 3209234 to a8500fe Compare May 16, 2023 20:49
@bjaglin bjaglin force-pushed the scalameta-deprecations branch from a8500fe to 5e77b05 Compare June 2, 2023 06:41
@bjaglin bjaglin closed this Jun 2, 2023
@bjaglin bjaglin force-pushed the scalameta-deprecations branch from 5e77b05 to 0501523 Compare June 2, 2023 11:18
@bjaglin bjaglin reopened this Jun 2, 2023
@bjaglin bjaglin force-pushed the scalameta-deprecations branch from 33845a5 to 289971f Compare June 3, 2023 09:19
@bjaglin bjaglin force-pushed the scalameta-deprecations branch from 289971f to 498b375 Compare June 3, 2023 09:30
@@ -181,7 +181,7 @@ To fix this bug, we first match function call nodes `Term.Apply` and pattern
match only `Lit.Boolean` that appear in argument position

```scala
case Term.Apply(_, args) =>
case Term.Apply.After_4_6_0(_, args) =>
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

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.

1 participant