Skip to content

Delayed parse-error on datapoint #28

@VictorCMiraldo

Description

@VictorCMiraldo

Because we are parsing the result of the merge too late, we are getting a different number of parse-errors:

Say that m = nonest and h=1 solves the conflict; this means that here we will try and parse M.lang;
which can raise a parse error.

Now say that m = proper didn't solve the conflict; we exit at once.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions