add more detail about implicit return

[jdv]

For instance, note that { "ret"; CATCH { default {} } } will not return "ret" which may be
counter-intuitive to some.

[salortiz]

I hope than in a future v6.x the non r-value phasers will be in some way re-moved/hidden/separated from the compiled execution tree of the block.
Meanwhile, its recommended position in the block should be at the top.

[MadcapJake]

Agreed, this tripped me up. To my eye, CATCH { ... } seems similar to a conditional branch but only runs if an error occurs, so with that assumption, it follows that the previous line would be the implicitly returning one. While I would enjoy that slight change to the semantics, it's definitely important we get this documented. The language/exceptions page could use at least one example showing a try/catch in a returning block and some discussion of this idiosyncrasy.

[AlexDaniel]

I think this may fit our traps page. I've been banging my head against this issue a couple of times.

[JJ]

So the position here is to add something to the traps page, right?

[AlexDaniel]

@JJ I think so, yes.

[JJ]

OK, I self-assign it, please feel free to help.

[AlexDaniel]

@JJ any progress?

[JJ]

Not really. I'll de-assign it, just in case you want to work on it.