-
Notifications
You must be signed in to change notification settings - Fork 21
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
quasiquotes sometimes require specific static types of splicees #6842
Comments
Imported From: https://issues.scala-lang.org/browse/SI-6842?orig=1 |
@xeno-by said: |
@densh said: |
@xeno-by said: This seems somewhat related to the situation with methods like Symbol.typeParams in the reflection API. The idea to move typeParams to TypeSymbol was, in principle, a good one. However, the fact that most of our symbol-related APIs return raw Symbol, which resulted in necessity to do mechanical casting. Here's another angle to view the situation. When we start using quasiquotes inside the compiler, we'll have to live with the fact that most of tree manipulation functions in the compiler return Tree, not specific subclasses of Tree. If quasiquotes are going to be too picky, we're going to have a lot of casting to do in the interim period. |
@densh said: |
@densh said: |
@Blaisorblade said (edited on Jan 20, 2014 5:29:21 AM UTC):
Hence, this should be reopened. |
@densh said: Documentation revamp is on my short list of things to be done before 2.11-RC1. |
@adriaanm said: |
The same goes for TypeDefs and CaseDefs.
The text was updated successfully, but these errors were encountered: