Using unresolved identifier in static context is not compile-time error anymore

[scheglov]

language/import_combinators_negative_test
language/unresolved_top_level_var_negative_test

From Gilad:

At this point this is a static warning and a runtime error. It looks like the spec omits to describe the static warning. I will fix this by adding:

It is as static warning if an identifier expression of the form id occurs inside a top level or static function (be it function, method, getter, or setter) or variable initializer and there is no declaration d with name id in the lexical scope enclosing the expression.

[DartBot]

This comment was originally written by rodion...@unipro.ru

---

In the wake of https://code.google.com/p/co19/issues/detail?id=332 that was recently filed by you:

There seems to be an inconsistency in how VM treats unresolved identifiers with and without arguments in a certain context.

Consider an example:

topLevelFunc() {
  declaredId; //library variable/getter/function object
  declaredId(args); // library function invocation
  (declaredId)(args); // same as above

  undeclaredId; // NoSuchMethodError
  undeclaredId(args); // compile-time error (implicit 'this' reference in a static/TL context) because there's no NSME clause in 12.14.3
  (undeclaredId)(args); // NSME again
}

same for a static context

This could be called counterintuitive

[anders-sandholm]

Removed this from the M2 milestone.
Added this to the M3 milestone.

[anders-sandholm]

Removed this from the M3 milestone.
Added this to the M4 milestone.

[larsbak]

Removed this from the M4 milestone.
Added this to the M5 milestone.

[kasperl]

Removed this from the M5 milestone.
Added this to the 1.6 milestone.

[kasperl]

Removed this from the 1.6 milestone.
Added Oldschool-Milestone-1.6 label.

[kasperl]

Removed Oldschool-Milestone-1.6 label.