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] Centralize type inference #281

Open
lucaneg opened this issue Mar 20, 2023 · 0 comments
Open

[FEATURE REQUEST] Centralize type inference #281

lucaneg opened this issue Mar 20, 2023 · 0 comments
Assignees
Labels
‼ priority:p1 Priority planning - level 1 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🛠 type:refactoring Refactoring of the codebase
Milestone

Comments

@lucaneg
Copy link
Member

lucaneg commented Mar 20, 2023

Description
Having type inference rules directly on symbolic operators makes it difficult to track what logic is being applied and requires redefinition of the operator to customize typing rules depending on the language. We could centralize the implementations in type systems.

@lucaneg lucaneg added 🛠 type:refactoring Refactoring of the codebase ‼ priority:p1 Priority planning - level 1 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms labels Mar 20, 2023
@lucaneg lucaneg added this to the 0.1b8 milestone Mar 20, 2023
@lucaneg lucaneg self-assigned this Mar 20, 2023
@lucaneg lucaneg added this to LiSA Mar 20, 2023
@lucaneg lucaneg moved this to Backlog in LiSA Mar 20, 2023
@lucaneg lucaneg modified the milestones: 0.1b8, 0.2 Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
‼ priority:p1 Priority planning - level 1 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🛠 type:refactoring Refactoring of the codebase
Projects
Status: Backlog
Development

No branches or pull requests

1 participant