Spec: execution of an expression handler after return is not documented?

[DartBot]

This issue was originally filed by ief...@unipro.ru

---

The spec v 0.07 states the following:

"Executing a return statement return e; first causes evaluation of the expression e, producing an object o. Next, control is transferred to the caller of the current function activation, and the object o is provided to the caller as the result of the function call."

I'm not sure I can see any sentence saying that needed finally clauses must be executed when return transfers control to a caller, e. g.

main() {
  try {
    return;
  } finally{
    print("finally!");
  }
}

Moreover, I can't see any hints about the following examples:

foo1() {
  try {
    return 1;
  } finally {
    return 2;
  }
}

foo2() {
  try {
    throw null;
  } finally {
    return 2;
  }
}

main() {
  print(foo1()); //2 should be printed
  print(foo2()); //2 should be printed
}

[iposva-google]

Set owner to @gbracha.
Added Area-Language, Triaged labels.

[gbracha]

The specification for the try statement addresses these concerns, as the rationale in that section states.
Rather than burden the entire specification with notions of abrupt and normal completion, the behavior of the try statement is defined with reference toe exception handlers that are always executed.

The plan is to add examples that will help make this clearer.

---

Added Invalid label.