single_match_else suggestion introduces violation of semicolon_if_nothing_returned

Summary

When applying the single_match_else suggestion, the output introduces a violation of semicolon_if_nothing_returned.

Reproducer

Code:

            match parse_char_escape(line) {
                Some(decoded) => result.push(decoded),
                None => {
                    result.push('\\');
                    result.push(line.current());
                    line.advance();
                }
            }

Current output:

            if let Some(decoded) = parse_char_escape(line) {
                result.push(decoded) // semicolon_if_nothing_returned
            } else {
                result.push('\\');
                result.push(line.current());
                line.advance();
            }

Desired output:

            if let Some(decoded) = parse_char_escape(line) {
                result.push(decoded);
            } else {
                result.push('\\');
                result.push(line.current());
                line.advance();
            }

Version

nightly

Additional Labels

No response

Start by reproducing the interaction between the single_match_else suggestion and the semicolon_if_nothing_returned lint using the Rust example in this issue. Trace the suggestion's generated output and verify that the resulting if-let branch includes the required semicolon and no longer triggers the second lint.