Skip to content

Confusing behaviour around compliment for "sugared" types #1222

@heshanpadmasiri

Description

@heshanpadmasiri

We represent subtypes of function, table, and object types internally using other basic types (lists and mapping). When we calculate the complement we need to make sure the top type is the corresponding top type (ie. function, table, or object) not the top type of the desugared type (list or mapping). This is supposed to be achieved by *SubtypeComplement functions,

However, it seems we can replace the top type in each of these cases with arbitrary types and nothing (except type serialization resulting in different Bdds) breaks (ie. top type doesn't seem to have an effect)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions