summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEugene Burmako <xeno.by@gmail.com>2013-02-05 00:35:16 +0100
committerEugene Burmako <xeno.by@gmail.com>2013-02-05 01:18:39 +0100
commit1093ce0b7c0d5e78dbd4cacc5c90cb264298afb0 (patch)
treeafb52072568be5de2661a4ff56cfc2aa139a8a25
parent7bf0ecc8d2d92b352182d61095bf564253f813d3 (diff)
downloadscala-1093ce0b7c0d5e78dbd4cacc5c90cb264298afb0.tar.gz
scala-1093ce0b7c0d5e78dbd4cacc5c90cb264298afb0.tar.bz2
scala-1093ce0b7c0d5e78dbd4cacc5c90cb264298afb0.zip
[nomaster] removes Tree.canHaveAttrs
This forward compatibility fix is very easy. Have a new method in 2.10.1? Don't expose it in the public API, and you won't have any problems.
-rw-r--r--src/reflect/scala/reflect/api/Trees.scala8
1 files changed, 0 insertions, 8 deletions
diff --git a/src/reflect/scala/reflect/api/Trees.scala b/src/reflect/scala/reflect/api/Trees.scala
index cfa6315797..38835d0f77 100644
--- a/src/reflect/scala/reflect/api/Trees.scala
+++ b/src/reflect/scala/reflect/api/Trees.scala
@@ -84,17 +84,9 @@ trait Trees { self: Universe =>
*
* Unfortunately `emptyValDef` is also considered to be `isEmpty`, but this is deemed to be
* a conceptual mistake pending a fix in https://issues.scala-lang.org/browse/SI-6762.
- *
- * @see `canHaveAttrs`
*/
def isEmpty: Boolean
- /** Can this tree carry attributes (i.e. symbols, types or positions)?
- * Typically the answer is yes, except for the `EmptyTree` null object and
- * two special singletons: `emptyValDef` and `pendingSuperCall`.
- */
- def canHaveAttrs: Boolean
-
/** The canonical way to test if a Tree represents a term.
*/
def isTerm: Boolean