From 1093ce0b7c0d5e78dbd4cacc5c90cb264298afb0 Mon Sep 17 00:00:00 2001 From: Eugene Burmako Date: Tue, 5 Feb 2013 00:35:16 +0100 Subject: [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. --- src/reflect/scala/reflect/api/Trees.scala | 8 -------- 1 file changed, 8 deletions(-) (limited to 'src/reflect') 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 -- cgit v1.2.3