ladybird/Tests/LibJS/Bytecode/input/invalid-lhs-assignment-no-dead-code.js

// Test that assigning to an invalid LHS (like a call expression)
// does NOT emit dead code after the Throw instruction.

function f(x) {
    x() = "foo";
}

try { f(() => {}); } catch {}
LibJS: Don't emit dead code after Throw for invalid LHS expressions When the left-hand side of an assignment, update, or for-in loop is invalid (e.g. `foo() = "bar"`), the bytecode generator emits a Throw instruction. Previously, it would also create a dead basic block after the Throw, resulting in unreachable instructions in the output. Fix this by returning early from the relevant codegen paths after emitting the Throw, and by guarding for-in/for-of body generation with an is_current_block_terminated() check. 2026-03-01 09:17:26 -03:00			`// Test that assigning to an invalid LHS (like a call expression)`
			`// does NOT emit dead code after the Throw instruction.`

			`function f(x) {`
			`x() = "foo";`
			`}`

			`try { f(() => {}); } catch {}`