Skip to content

refactor: investigate removing conversion of ParseErrors to RuntimeErrors thus removing ASTError #6711

@jacinta-stacks

Description

@jacinta-stacks

Should parse errors ever be converted to runtime errors? ASTError seems to only happen from calls in unit tests OR in clarity-cli.

Metadata

Metadata

Assignees

No one assigned

    Labels

    aacAvoiding Accidental Consensus

    Type

    Projects

    Status

    Status: 🆕 New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions