-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Fix ambiguous unapply for TASTy reflect Parent #4998
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
nicolasstucki
merged 1 commit into
scala:master
from
dotty-staging:fix-parents-tasty-reflect
Aug 26, 2018
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -306,4 +306,5 @@ trait TreeOps extends TastyCore { | |
} | ||
} | ||
|
||
implicit def termAsParent(term: Term): Parent | ||
} |
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
33 changes: 33 additions & 0 deletions
33
tests/pos-special/fatal-warnings/tasty-parent-unapply.scala
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
import scala.quoted._ | ||
|
||
import scala.tasty.Tasty | ||
|
||
object Macros { | ||
|
||
|
||
def impl(tasty: Tasty): Unit = { | ||
import tasty._ | ||
|
||
def foo(tree: Tree, term: Term, typeTree: TypeTree, parent: Parent) = { | ||
|
||
tree match { | ||
case IsTerm(tree) => | ||
} | ||
|
||
term match { | ||
case IsTerm(term) => | ||
} | ||
|
||
typeTree match { | ||
case IsTypeTree(typeTree) => | ||
} | ||
|
||
parent match { | ||
case IsTerm(typeTree) => | ||
case IsTypeTree(typeTree) => | ||
} | ||
|
||
} | ||
} | ||
|
||
} |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems dangerous to me, as any term can now be disguised as
Parent
. The same forTypeTree
. Conceptually, how it is different from makingParent
a supertype ofTerm
andTypeTree
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not conceptually different, but it solves the ambiguity in the extractor when passing a
Term
as term could be aTree
or aParent
. This will be removed when we bootstrap and I'll be able to definetype Parent = Term | TypeTree
and have a simple extractor for both.