Skip to content

location information in parsing rejections #338

Description

@Smattr

rumur has a nice setup where unsupported features surface with line and column information, and even colour. Other tools like murphi2c just report unsupported features with no location. It would be helpful if they also carried a pointer to exactly what in the input file was causing the rejection.

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