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

[FEATURE REQUEST] Base implementation for FunctionalLattice's isTop() and isBottom() #184

Closed
lucaneg opened this issue Feb 8, 2022 · 0 comments · Fixed by #195
Closed
Assignees
Labels
⁉ priority:p2 Priority planning - level 2 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🎆 type:feature New feature or request
Milestone

Comments

@lucaneg
Copy link
Member

lucaneg commented Feb 8, 2022

Description
A base implementation of FunctionalLattice's isTop() and isBottom() methods should be provided as the one defined in Environment, since that one is usually the logic for environments. It might also be worth investigating default implementations for SetLattice and InverseSetLattice.

@lucaneg lucaneg added 🎆 type:feature New feature or request ⁉ priority:p2 Priority planning - level 2 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms labels Feb 8, 2022
@lucaneg lucaneg added this to the 0.1b5 milestone Feb 8, 2022
@lucaneg lucaneg self-assigned this Feb 8, 2022
@lucaneg lucaneg modified the milestones: 0.1b5, 0.1b6 Feb 21, 2022
@lucaneg lucaneg added the 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet label Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⁉ priority:p2 Priority planning - level 2 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🎆 type:feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant