Fixes #[issue number from problem statement]

Problem

When a yield break statement appeared in a catch block within a try-catch-finally structure in an async iterator method, the compiler generated invalid IL that failed ILVerify with the error:

[MoveNext]: Leave into try block. { Offset = 0x11a }

This occurred because the compiler placed a finallyEntry label at the end of the try block to handle disposal mode jumps. When a yield break in a catch block tried to leave to this label, it created invalid IL - you cannot leave from a catch block into its associated try block.

Example

public static async IAsyncEnumerable<int> M()
{
 try
 {
 try { yield break; }
 finally { throw null; }
 }
 catch
 {
 yield break; // This generated invalid IL
 }
 finally { }
}

Solution

Modified AsyncIteratorMethodToStateMachineRewriter.cs to intelligently place the finallyEntry label based on whether the try statement has catch blocks:

• Without catch blocks: Place the label at the end of the try block (original behavior, valid IL)
• With catch blocks: Place the label after the entire try-catch-finally structure (new behavior, valid IL)

This ensures both try blocks and catch blocks can validly leave to the finallyEntry label, and the finally block executes properly before continuing disposal.

Testing

• The TryFinally_YieldBreakInDisposeMode test now passes without requiring Verification.FailsILVerify
• All 283 async iterator tests pass, confirming no regressions
• The generated IL now passes ILVerify validation

Fixes #79124

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.