Feature Request: Motif Scopes should automatically provide all the interfaces that they implement as bindings within the scope

[andreasnomikos]

A common and useful pattern is as follows

public class Foo(ParentComponent) {

public interface ParentComponent {
  Bar bar()
}
}

This pattern allows every single class that defined to somewhat act as its own "scope" with a clear api towards the outside world

to better support this pattern motif.Scopes should automatically provide all the interfaces that they implement as bindings

@motif.Scope
interface  Scope extends Foo.ParentComponent {

 @motif.Objects 
 abstract class Objects {
    abstract Foo foo();

    abstract Foo.ParentComponent fooParent(Scope scope) <-- this declaration could be now be avoided 
 }
}

[Leland-Takamine]

Are there any cases you can think of where the automatic provision of the extended interfaces would be problematic?

[andreasnomikos]

Yes we can't @expose them