So the documentation for return() says plainly that it will return from a lambda, ending evaluation of the function.
If called from within a lambda the return will return from the function evaluating the lambda.
So let's build a short manifest and use a function that evaluates a lambda:
This creates an error:
Reading the spec test confirms that this is expected behavior?
I thought of perhaps creating this as a documentation bug, but this is failing on documented (and desirable) functionality.