Adds `DartOptions` to generic method syntax tests.

Adds `DartOptions` to generic method syntax tests.

This CL adds a `DartOptions` comment to the '--generic-method-syntax'
related tests specifying that option, and changes the entries for these
tests in status files to expect success for dart2js except when running
in a browser (where the option gets dropped rather than passed on to
the compiler).

BUG=
R=floitsch@google.com

Committed: https://github.com/dart-lang/sdk/commit/ae31db041d192232c2e65e10577c17689be6e747

[eernst, 2016-05-09 13:13:01]

Description was changed from

==========
Adds `DartOptions` to generic method syntax tests.

This CL adds a `DartOptions` comment to the '--generic-method-syntax'
related tests specifying that option, and changes the entries for these
tests in status files to expect success for dart2js except when running
in a browser (where the option gets dropped rather than passed on to
the compiler).
==========

to

==========
Adds `DartOptions` to generic method syntax tests.

This CL adds a `DartOptions` comment to the '--generic-method-syntax'
related tests specifying that option, and changes the entries for these
tests in status files to expect success for dart2js except when running
in a browser (where the option gets dropped rather than passed on to
the compiler).

BUG=
==========

[eernst, 2016-05-09 13:32:11]

eernst@google.com changed reviewers:
+ johnniwinther@google.com

[eernst, 2016-05-09 13:32:11]

This CL uses a `DartOptions` comment to make test.py pass
'--generic-method-syntax' to dart2js when running the generic method related
tests.

An issue arose while doing that: The documentation around DartOptions in
test_suite.dart says that "Flags can be passed to the dart script that contains
the test", but that sounds like a very different thing (we must be running
`dart2js .. --generic-method-syntax x.dart` where 'x.dart' is the test file
path, and that's not passing '--generic-method-syntax' to 'x.dart').

So did I misunderstand that, or should I file a bug against test_suite.dart (or
test.py, or something in between)?

[floitsch, 2016-05-09 15:04:58]

floitsch@google.com changed reviewers:
+ floitsch@google.com

[floitsch, 2016-05-09 15:04:58]

LGTM.

Just fix the documentation for DartOptions.

[eernst, 2016-05-09 15:15:43]

Description was changed from

==========
Adds `DartOptions` to generic method syntax tests.

This CL adds a `DartOptions` comment to the '--generic-method-syntax'
related tests specifying that option, and changes the entries for these
tests in status files to expect success for dart2js except when running
in a browser (where the option gets dropped rather than passed on to
the compiler).

BUG=
==========

to

==========
Adds `DartOptions` to generic method syntax tests.

This CL adds a `DartOptions` comment to the '--generic-method-syntax'
related tests specifying that option, and changes the entries for these
tests in status files to expect success for dart2js except when running
in a browser (where the option gets dropped rather than passed on to
the compiler).

BUG=
R=floitsch@google.com

Committed:
https://github.com/dart-lang/sdk/commit/ae31db041d192232c2e65e10577c17689be6e747
==========

[eernst, 2016-05-09 15:15:45]

Committed patchset #1 (id:1) manually as
ae31db041d192232c2e65e10577c17689be6e747 (presubmit successful).