#### §B.2.(3) Between OTJLD 1.2 and OTJLD 1.3

- §2.1.1 : Binding roles to base interfaces

  The implementation limitation mentioned in §2.1.1 has been mostly removed.

- §2.3.1.(d) : Fine-tuning role instantiation

  An annotation has been defined for modifying the semantics of lifting in order to improve performance. Also a new section has been added as §6.3 to summarize the annotation types defined in this document.

- §2.3.5 : Consequences of lifting problems

  After §2.3.4 has clarified that `LiftingFailedException` (§6.2.(d)) is indeed a checked exception, a subsection has been added defining the consequences of this exception in various program situations.

- §3.1.(k) : Callout to generic method

  Added a rule on how a callout binding may refer to a generic base method.

- §4.1.(b) : Callin binding in "unliftable" role

  Callin bindings can now be defined even in "unliftable" roles.

- §4.1.(h) : Binding to team methods

  `before` and `after` callin bindings can now bind to methods of an enclosing class, too.

- §4.8.(d) : Order when merging precedence declarations

  Clarified how several precedence declarations are merged, which was underspecified, because the C3 algorithm needs ordered inputs, but this order was not specified.

- §4.10.(e) : Propagating type parameters in callin bindings

  In addition to capturing covariant return types, a callin binding may also declared type parameters in order to propagate genericity from its base method to the role method.

- §5.3.(d) : Configuring implicit activation

  Mechanisms have been added for configuring implicit team activation. The default has been changed to not apply implicit activation. A corresponding note has also been added to §5.3

- §9.2.1.(a) : Instance constrained type parameter

  Type anchors can now be applied to type parameters, too, thus expressing a new kind of constraint on the type parameter.