Investigate simplifying contributing multiple bindings with less code

[ZacSweers]

Couple ideas

Investigate supporting @Contributes*Binding annotations on supertypes directly. Requires ensuring they're in metadata. Less sure about readability here

@Inject
class CacheImpl :
  @ContributesBinding(AppScope::class)
  Cache,
  @ContributesBinding(AppScope::class)
  AnotherType,
  @ContributesBinding(AppScope::class)
  YetAnotherType {
  override fun toString(): String = "CacheImpl"
}

Make binding vararg, perhaps as an additionalBindings vararg to match the existing scope/additionalScopes patterns.

@Inject
@ContributesBinding(
  AppScope::class,
  binding<Cache>(),
  binding<AnotherType>(),
  binding<YetAnotherType>(),
)
class CacheImpl : Cache, AnotherType, YetAnotherType

[ZacSweers]

did a little tinkering on the first one but bad news. While they are visible in metadata, supertypes aren't resolved yet at the phase of the compiler that we generate hints from. We could possibly manually resolve them early, but does feel like I'd be working against the compiler phases for this. I think additionalBindings is going to be the better approach for now barring moving all merging to IR

[ZacSweers]

I'm not sure anymore about this case. What happens if someone writes this?

@Inject
@ContributesBinding(
  AppScope::class,
  binding<Cache>(),
  binding<AnotherType>(),
  binding<YetAnotherType>(),
  replaces = [Something::class],
)
class CacheImpl : Cache, AnotherType, YetAnotherType

[ZacSweers]

from some offline conversation

@Inject
@ContributesBinding(
  AppScope::class,
  binding<Cache>(replaces = [Something::class]),
  binding<AnotherType>(),
  binding<YetAnotherType>(replaces = [Something::class]),
)
class CacheImpl : Cache, AnotherType, YetAnotherType

Is another option