Function literal with square brackets not an assignable expression

[DartBot]

This issue was originally filed by [email protected]

---

Spec (0.08) says:

ch 10 - function literal is a primary:
primary:
...
functionExpression |
...

10.27:
assignableExpression:
primary (argument* assignableSelector)+ |
super assignableSelector |
identifier
;

assignableSelector:
[' expression]' |
`.' identifier
;

which should mean that something like 'void foo() {}[0]' is an assignable expression and can be used with a postfix operator:

postfixExpression:
assignableExpression postfixOperator |
...

However, the following test fails on VM:
'file:///media/sf_dart_local/co19/tests/co19/src/Language/10_Expressions/26_Postfix_Expressions_A01_t01.dart': Error: line 64 pos 26: expression is not assignable
    try { void f() {} [0]++; } catch(var e) {}
                         ^

might be related to issue #1189

[DartBot]

This comment was originally written by [email protected]

---

The same productions lead us to believe that the following should be allowed (but isn't):

Error: line 65 pos 22: unexpected token '.'
    try { void f() {}.x; } catch(var e) {}
                     ^
    try { void f() {}.x++; } catch(var e) {}
                     ^

[madsager]

Added Area-VM, Triaged labels.

[iposva-google]

Set owner to @gbracha.
Added Accepted label.

[gbracha]

Once we finalize 1676 and 1189 we'll be able to proceed on this.

[iposva-google]

Gilad, any update?

[gbracha]

Function expressions have changed since this was filed (and so has try-catch). Function expressions have no return type and no name, so the examples should now look like this:

  try { () {}.x; } catch(e) {};
  try { () {}.x++; } catch(e) {};

these are syntactically legal (though they give rise to warnings and will fail at runtime). So I think the issue is moot.

[iposva-google]

Removed Priority-Medium label.
Added Priority-Unassigned label.

[iposva-google]

Interpreting "issue is moot" as "AssumedStale".

[iposva-google]

Added AssumedStale label.