docs

Author: adriaanm

src/compiler/scala/tools/nsc/transform/Mixin.scala

@@ -14,15 +14,23 @@ import scala.collection.{ mutable, immutable }
   *
   * So far, we've tried to treat classes and traits in the same way as much as possible.
   * Except, for traits:
-  *   - no field symbols are entered (pretend the val is abstract)
-  *   - lazy val is an abstract getter and a concrete method to compute the rhs (and perform its side-effects)
-  *   - accessors for fields, outer pointers and super calls are abstract
+  *   - Fields have been removed during Constructors, which also made their accessors abstract,
+  *     while setting the MIXEDIN flag to track that the accessors need to be implemented here.
+  *     (Constructors needs to see the fields to the init code to the constructor.
+  *      Note that getters for vals without storage are concrete already in the trait -- see `typeNeedsNoStorage`)
+  *   - An outer accessor is abstract
+  *   - A super accessor is abstract
+  *   - A lazy val is an abstract getter and a concrete method to compute the rhs (and perform its side-effects)
+  *   - TODO: (lifted) objects
   *
   * In classes that extends traits, it's time to face the music:
-  *   - an overriding method is added for each trait method definition with the override keyword (TODO: refine)
+  *   - an overriding method is added for each trait method definition with the override keyword,
+  *     as well as for each method that occurs more than once in the linearisation:
+  *       ```trait A { def foo }; trait B { def foo}; class C extends A with B { /* must override foo */ }```
   *   - fields are created
   *   - accessors are implemented (for fields, outers & supers)
   *   - lazy vals get bitmaps, getter does its lazy thing, using the compute method in the trait
+  *   - TODO: (lifted) objects
   *
   *
   */