type return/break/continue expressions with monomorphs instead of Dynamic (see #10744)

[nadako]

this is what we already do for throw since 2008 (9cee2fc)

[nadako]

I'm wondering if we should be a bit more clever and type all terminators as Void if they are used in WithType.NoValue context. Less monomorphs is always better, and we could save some memory with this, I guess.

(ideally we of course want a bottom type but that's a different topic)

[nadako]

I'm wondering if we should be a bit more clever and type all terminators as Void if they are used in WithType.NoValue context.

Tried that quickly and ran into problems with inlined returns, so it needs more investigation.

[Simn]

@ncannasse You wouldn't happen to remember why this was typed as Dynamic? I recall discussing this with you like 10 years ago and it made sense to me at the time, but now I'm not really seeing why this should be the case.

[Simn]

Looking at this again, I wonder if we should only create monomorphs for this when we're typing a value. I don't see what we gain by creating monos for any block-level return expression and such. I'm actually trying to have less wild monos floating around, so this would work a bit against that.

What do you think?

[nadako]

Makes sense. I think I've tried that but had some issue with inlining and didn't have time to figure it out since then...

[nadako]

should it be Void maybe?

[Simn]

I'm a bit worried about some crazy inline situation where we end up with Void in a value-place... With Dynamic we at least have the same behavior as before.