First step of support for parsing and ignoring generic methods.

tests/language/language_analyzer2.status

Index: tests/language/language_analyzer2.status
diff --git a/tests/language/language_analyzer2.status b/tests/language/language_analyzer2.status
index 5f20feae954cf27bcbcc27a65fea1cea4c5e94df..f7b3274eabe2e6758bb9b2ff607eecde9309c747 100644
--- a/tests/language/language_analyzer2.status
+++ b/tests/language/language_analyzer2.status
@@ -520,3 +520,7 @@ accessor_conflict_import2_test: StaticWarning # Issue 25624
 accessor_conflict_import_prefixed2_test: StaticWarning # Issue 25624
 accessor_conflict_import_prefixed_test: StaticWarning # Issue 25624
 accessor_conflict_import_test: StaticWarning # Issue 25624
+
+# Experimental feature: generic methods.
+generic_functions_test: CompileTimeError # Not yet implemented.

[floitsch, 2016/02/22 12:45:20]

The analyzer already supports generic methods. not sure if they expose a flag,
though.

[eernst, 2016/02/22 18:02:51]

Haven't been able to spot a suitable issue number for the analyzer. Sent mail to
Brian in order to learn more about the possible flag and the issue number.

[floitsch, 2016/02/22 18:40:27]

The options file supports it:
$ cat /tmp/options
analyzer:
  language:
    enableGenericMethods: true

$ dartanalyzer --options=/tmp/options gen_methods.dart

Note, that the analyzer needs to change its behavior (or provide a different
flag), since it currently does semantic checks too.
The syntactic parser exists, though.

[eernst, 2016/02/23 12:40:45]

Using that, checking that it does not produce any diagnostics.

We do fail to test the cases where programs are syntactically correct but fail
during static semantic checking, but that seems
to be an unimportant case: Checking that a semantically correct program is also
syntactically correct should be enough, and it is the only combination which
remains interesting also when the implementation has been made more complete.

+generic_methods_test: CompileTimeError # Not yet implemented.