-
Notifications
You must be signed in to change notification settings - Fork 35
Closed
Labels
‼ priority:p1Priority planning - level 1Priority planning - level 1🌍 scope:interprocWork regarding interprocedural analyses or call graphsWork regarding interprocedural analyses or call graphs🎆 type:featureNew feature or requestNew feature or request🎊 resolution:resolvedBug or feature resolved - might not have been merged to master yetBug or feature resolved - might not have been merged to master yet
Milestone
Description
Description
Right now we can only tune the type of dispatch (static vs. dynamic) of the parameters, but one cannot redefine how the matching is done. For instance, right now the final implementation contained in UnresolvedCall.ResolutionStrategy checks if the number of arguments of the implementation and the call is the same, and only in this case try to match the arguments. We should make this flexible and parametrize the analysis over a ResolutionStrategy.
Motivation
For instance in Python one might call a method with a different number of parameters (because some have default values), by matching them by name and not by position, and the match is done only by name.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
‼ priority:p1Priority planning - level 1Priority planning - level 1🌍 scope:interprocWork regarding interprocedural analyses or call graphsWork regarding interprocedural analyses or call graphs🎆 type:featureNew feature or requestNew feature or request🎊 resolution:resolvedBug or feature resolved - might not have been merged to master yetBug or feature resolved - might not have been merged to master yet