Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confusing behaviour around compliment for "sugared" types #1222

Open
heshanpadmasiri opened this issue Jul 27, 2023 · 1 comment
Open

Confusing behaviour around compliment for "sugared" types #1222

heshanpadmasiri opened this issue Jul 27, 2023 · 1 comment

Comments

@heshanpadmasiri
Copy link
Member

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)

@heshanpadmasiri
Copy link
Member Author

looping in @lochana-chathura

@heshanpadmasiri heshanpadmasiri added question Further information is requested Type/Question and removed question Further information is requested labels May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants