`es/minifier`: remaining cases where IIFE isn't invoked

[Le0Developer]

Describe the feature

More or less a tracking issue for the points in #10220

• comma expressions (return inlineMe(), 123) implemented in es/minifier: IIFE Invoker should invoke more arrow functions, like in sequence expressions #10859
• value in ternary expression (return cond ? inlineMe() : 123)
• return in loop (labelled break?)
• simple condition (if(inlineMe()) { ... }/inlineMe() ? ... : ...)
• short circuiting (return cond && inlineMe())

Babel plugin or link to the feature description

No response

Additional context

Sorted by my subjective opinion of implementation complexity (while barely knowing anything of the swc internals).

[Austaras]

How could scenario 2 be inlined?

For scenario 4 and 5, it's possible to use a tempoaray value, but I highly doubt it would be benefitical to gzipped size judging from past history.

[gkgoat1]

How could scenario 2 be inlined?

If we undo if statement compression, the inline opportunity would be revealed, and then, after inlining, we can recompress the if statements

For scenario 4 and 5, it's possible to use a tempoaray value, but I highly doubt it would be benefitical to gzipped size judging from past history.

[Austaras]

How could scenario 2 be inlined?

If we undo if statement compression, the inline opportunity would be revealed, and then, after inlining, we can recompress the if statements

This would create extra if and return. I don't believe it would be beneficial for the eventual size