Skip to content

[PyVCG] Refactor Optional components #220

Description

@hoe-jo

each optional component/tuple field is modeled as a value symbol plus a separate .valid boolean constant, manually threaded through checks (e.g. trlc/vcg.py, trlc/vcg.py).

PyVCG 1.0.10's native Optional sort/Optional_Null_Check/Optional_Value could replace this pattern with a single first-class SMT type instead of the manual value/valid pair.

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