Binding @Spreads

[mcassiano]

Should we be able to do something like:

interface Component {
  fun a(): A
}

@Spread
abstract fun bindComponent(component: Component): Component

And then local scope would be able so directly see A. Right now we fail because of a dependency cycle.

[mcassiano]

Adding a qualifier to the return type makes it work gracefully. I think this can be treated as a bug. I can send in a pull request if this is a wanted feature.

[andreasnomikos]

how are you going to treat the presence of Qualifiers in this case ?
This api will create an imbalance for methods tagged with @SPREAD.
currently all methods in @objects contribute the returned type+qualifier to the graph. with the proposed change
@SPREAD methods will be treated differently than other methods.

because this will be a breaking api change I don't think this PR will be advisable.

Adding the Qualifier to increase clarity is not a big overhead IMO.

[mcassiano]

I wouldn't qualify types with @SPREAD, rather make Sinks/Sources not raise a cycle error in this case. I'm ok with not "fixing" this, but I think there's opportunity to at least document this case?

[andreasnomikos]

Better documentation sounds great.