Handle top-level methods called export, etc. #28808

Open
peter-ahe-google opened this Issue Feb 17, 2017 · 0 comments

Projects

None yet

1 participant

@peter-ahe-google
Contributor

Fasta's parser is confused when one of the built-in identifiers export, import, library, part, or typedef appears as the name of a top level function with an implicit return type.

Examples from parser_test.dart:

    parseCompilationUnit('abstract(x) => 0;');
    parseCompilationUnit('as(x) => 0;');
    parseCompilationUnit('dynamic(x) => 0;');
    parseCompilationUnit('export(x) => 0;');
    parseCompilationUnit('external(x) => 0;');
    parseCompilationUnit('factory(x) => 0;');
    parseCompilationUnit('get(x) => 0;');
    parseCompilationUnit('implements(x) => 0;');
    parseCompilationUnit('import(x) => 0;');
    parseCompilationUnit('library(x) => 0;');
    parseCompilationUnit('operator(x) => 0;');
    parseCompilationUnit('part(x) => 0;');
    parseCompilationUnit('set(x) => 0;');
    parseCompilationUnit('static(x) => 0;');
    parseCompilationUnit('typedef(x) => 0;');

@stereotype441

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment