I have
trait Invoker { val method: Method }
Intellij IDEA code inspection is warning me that "Abstract value used in trait". Everything compiles fine. Is there something wrong with having an abstract value in a trait? If so, how should I specify that all extenders of the trait must define a method property?
A class can extend only one abstract class, but it can implement multiple traits, so using traits is more flexible.
Trait supports multiple inheritance. Abstract Class supports single inheritance only. Trait can be added to an object instance. Abstract class cannot be added to an object instance.
In Scala, an abstract class is constructed using the abstract keyword. It contains both abstract and non-abstract methods and cannot support multiple inheritances. A class can extend only one abstract class. The abstract methods of abstract class are those methods which do not contain any implementation.
In scala, trait is a collection of abstract and non-abstract methods. You can create trait that can have all abstract methods or some abstract and some non-abstract methods. A variable that is declared either by using val or var keyword in a trait get internally implemented in the class that implements the trait.
What is meant by this is the following weirdness:
trait A { val i: String def j: String } class C extends A { println ("val i = " + i) println ("def j = " + j) val i = "i" def j = "j" } val c = new C // prints // val i = null // def j = j
So, as you can see i
is initialised to it default value (null
for AnyRef
) before it is finally overridden by the constructor in C
. (def
declarations are re-referenced immediately.)
To avoid this one would have to put the val
initialisations to the beginning of the constructor, if possible.
Additional weirdness (and how to solve it) in the following case
Consider
trait A { val i: String def j: String } abstract class D extends A { println ("val i = " + i) println ("def j = " + j) } class C extends D { val i = "i" def j = "j" } val c = new C // prints // val i = null // def j = null
Now we seem to be out of luck; it looks as if there is no chance for us to initialise val i
and def j
before our superclass D
tries to print them. In order to solve this problem, we must use Early definitions (§5.1.6 Scala reference):
class C extends { val i = "i" def j = "j" } with D val c = new C // prints // val i = i // def j = j
And it works!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With