[M3devel] An awkward interaction of language properties

[Mika Nystrom]

Yes I should think if you declare the Container type in one interface,
to be <: ROOT you can then refer to that from the other interfaces.
Then you REVEAL the actual details in another interface that's not
imported by the others but only where it is needed.  Both the interfaces
you have can be generic.

    Mika


Henning Thielemann writes:
>
>On Fri, 17 Feb 2012, Rodney M. Bates wrote:
>
>> The only way I can think of is to make the Relatives field be a REFANY,
>> and not import DTContainer into DataStruct2.  This loses static safety,
>> but at least it will be replaced by dynamic safety, at the cost of
>> runtime narrow checks every time I use Relatives.
>
>Some REVEAL tricks instead of REFANY?