Why was JAB0014 introduced? about jab

[pakrym]

There are multiple valid ways to express the idea of a dependency being optional when designing a class in C#:

class Foo { public Foo(Bar? bar); }
class Foo { public Foo(Bar? bar = null); }

But only one aligns with how Jab resolution rules are set up. The diagnostic highlights that there might be a misalignment between customer expectations and Jab logic.

Think about it similar to compiler highlighting if (a == null) check when a is annotated as non-nullable. The code is fine, but the branch will never fire.

[Marv51]

Thanks for the explanation