"MissingBinding" error when a type is injected as both nullable and non-nullable

[Egorand]

Description

This seems to be a regression in 0.10.1: if a type has both nullable and non-nullable injection sites, compilation will fail with the following error:

error: [Metro/MissingBinding] Cannot find an @Inject constructor or @Provides-annotated function/property for: Foo

    Foo is injected at
        [AppGraph] View1(…, foo)
    View1 is requested at
        [AppGraph] AppGraph.view1

Similar bindings:
  - Foo? (Nullable equivalent). Type: ConstructorInjected. Source: NullableNonNullableInject.kt:3:1

Self-contained Reproducer

class Foo @Inject constructor()

class View1 @Inject constructor(foo: Foo)
class View2 @Inject constructor(foo: Foo?)

@DependencyGraph
interface AppGraph {
  val view1: View1
  val view2: View2
}

fun box(): String {
  val graph = createGraph<AppGraph>()
  val view1 = graph.view1
  val view2 = graph.view2
  return "OK"
}

Metro version

0.10.1

Context

Initially reproduced in cash-android, and was later reproduced in the metro repo with a unit test.

[ZacSweers]

This is working as intended and has always been the behavior, you'll need to add a binding to the nullable one if you want it to satisfy it because it won't do it implicitly

Not sure why this didn't fail for you before though, the logic for this didn't change in 0.10.1 either 🤔

[ZacSweers]

Actually this is legit and it's just coincidence that it's reporting it on main I think. Let me harden this logic