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.

Sign up for GitHub

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

Jump to bottom

[FEATURE REQUEST] Parametrize scoping logic around calls #301

Open
lucaneg opened this issue Dec 11, 2023 · 0 comments
Open

[FEATURE REQUEST] Parametrize scoping logic around calls #301

lucaneg opened this issue Dec 11, 2023 · 0 comments
Assignees
@lucaneg
Labels
‼ priority:p1 Priority planning - level 1 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🌍 scope:interproc Work regarding interprocedural analyses or call graphs 🎆 type:feature New feature or request
Milestone
0.2

Comments

@lucaneg
Copy link
Member

lucaneg commented Dec 11, 2023

Description
Depending on the language, the scoping mechanism when a call is encountered might be different. The LanguageFeatures class should contain a ScopingStrategy that allows to customize how the analysis behaves around calls (not only if/when scoping should be applied, but also to which portion of the state).
@lucaneg lucaneg added 🎆 type:feature New feature or request ‼ priority:p1 Priority planning - level 1 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🌍 scope:interproc Work regarding interprocedural analyses or call graphs labels Dec 11, 2023
@lucaneg lucaneg added this to the 0.2 milestone Dec 11, 2023
@lucaneg lucaneg self-assigned this Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lucaneg lucaneg

Labels
‼ priority:p1 Priority planning - level 1 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🌍 scope:interproc Work regarding interprocedural analyses or call graphs 🎆 type:feature New feature or request
Projects
LiSA
Status: Backlog
Milestone
0.2
Development

No branches or pull requests
1 participant
@lucaneg