Failed to produce diagnostic with optionals and generics (minimal repro)

[tristanlabelle]

Description
The Swift compiler produces a fatal error when compiling a combination of generics and optionals.

Steps to reproduce
Compile the following with swiftc:

class Repro {
    func foo(repro: Repro?) { _ = repro?.bar() }
    func bar<T>() -> T { fatalError("") }
}

Output:

Building for debugging...
C:\Code\browser-swift\Apps\BrowserWin\Source\Application\ArcApplication.swift:2:33: error: failed to produce diagnostic for expression; please submit a bug report (https://swift.org/contributing/#reporting-bugs)
    func foo(repro: Repro?) { _ = repro?.bar() }
                                ^
error: fatalError

Expected behavior
A diagnostic should be produced and the compiler should not fatalError

Environment

• Swift compiler version info: February 27, 2023 snapshot on Windows

compnerd.org Swift version 5.9-dev (LLVM 84aca0981812b32, Swift a0e1810f627add5)
Target: x86_64-unknown-windows-msvc

• Xcode version info: N/A
• Deployment target: N/A

[xedin]

Looks like we binding type variable allocated for optional evaluation expression to the one that represents generic parameter and that ends up propagating "can be hole" trait to the former one without a fix.

[xedin]

cc @LucianoPAlmeida maybe interesting, I wonder if we need to change constraint generation for optional evaluation expression slightly to avoid this kind of problem.

[LucianoPAlmeida]

I remember this one, is the propagation logic we have for optional evaluation right?
Was taking a look at the comment and it was mainly for pattern context, but now that pattern variables are marked as holes this propagation is still needed? Maybe I am missing something or it still needed in general.
What is the idea on adjusting CSGen logic?