Skip to content

Parser failure when EOF exists where semicolon is expected at end of statement #5

@csnover

Description

@csnover

EOF should be considered a valid statement terminator, but currently it generates an error. For example, given the following code:

foo()

the following error is generated: [2, 5]unexpected token (tEof:'EOF'); expected ;

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions