Representing Scala types in class diagrams?

Oops... made some typos. The code was meant to be:

trait BaseComponent { self: BaseComposite => }
trait BaseComposite extends BaseComponent

trait SpecializedComponent extends BaseComponent { self:
SpecializedComposite => }
trait SpecializedComposite extends BaseComposite with SpecializedComponent

Erkki Lindpere wrote:
> Java has the nice property of mapping very well to UML class diagrams.
> Has anyone thought about how well they can represent all the possible
> Scala types or if not, then how to do diagrams for Scala code?
>
> For example:
>
> trait BaseComponent { self: Composite => }
> trait BaseComposite extends BaseComponent
>
> trait SpecializedComponent { self: SpecializedComposite => }
> trait SpecializedComposite extends BaseComposite with
> SpecializedComponent
>
> How to represent this? I came up with the following (see attached PNG)
>
> Erkki
>
>
> ------------------------------------------------------------------------
>

Hi Erkki,

AFAIK there has not been much thought about representing Scala's type
relationships in UML.
The closest thing I know of is the notation in our Scalable Component
Abstractions paper and in the thesis of Matthias Zenger. But that's in
a way more general and does not deal specifically with selftype
annotations. I quite like the way you approach this.

Cheers