Equivalent guard-case
expressions produce different results in Swift Testing’s #expect
(compiler crash)
#76765
Labels
availability
The @available attribute and availability checking in general
bug
A deviation from expected or documented behavior. Also: expected but undesirable behavior.
triage needed
This issue needs more specific labels
Description
Two seemingly equivalent
guard-case
expressions result in different outcomes when they’re used inside an#expect
call in Swift Testing:I reported this in the Swift Testing repo. @stmontgomery suggested this could be caused by a compiler crash.
Crash backtrace
Reproduction
I was able to reproduce the issue in multiple iOS projects, including a newly-created one.
The following code causes the crash:
Complete file
Expected behavior
The two
guard-case
expressions can be used interchangeably.Environment
Additional information
guard-case
expressions #76770The text was updated successfully, but these errors were encountered: