VM allows this initializers of private fields in constructors.

[DartBot]

This issue was originally filed by zundel@google.com

---

// Spec. version 6.2.2: It is a compile-time error if a named formal parameter begins with an '_'

class Foo {
  num _y;
  Foo.optional_private([this._y = 77]) {} // illegal named parameter starts with _
}

main() {
  var obj;
  obj = new Foo.optional_private(_y: 222);
  Expect.equals(222, obj._y);

  obj = new Foo.optional_private();
  Expect.equals(77, obj._y);
}

See forthcoming parameter_initializer6_negative_test

Comment from gbracha: "Yes, that is illegal per the spec. It might be easier to deal with this once we add positional optional parameters, which should be coming to a spec near you in the near future. "

There are some libraries that currently violate this rule and I'm cleaning them up before I commit the new test:

http://codereview.chromium.org/10541095/

[iposva-google]

Set owner to @kmillikin.

[iposva-google]

Is this still a valid bug report?

---

Set owner to @gbracha.

[gbracha]

Yes. The spec still says that named parameters cannot be have their name start with _.

[iposva-google]

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

[DartBot]

This comment was originally written by @mhausner

---

Added Started label.

[DartBot]

This comment was originally written by @mhausner

---

Set owner to @mhausner.

[DartBot]

This comment was originally written by @mhausner

---

https://codereview.chromium.org/23478005/
Committed at 26719

---

Added Fixed label.