You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've implemented a first rough draft. It attaches the hotspots to the methods where the invocations take place. In an improved version, I'd rather attach the hotspots to the invoked methods... (but couldn't yet figure out how to do that)
This statistics additionally raises the following questions:
Should we disregard invocations of methods that are not under Usus control (e.g. framework methods)? (I think yes)
Should we disregard methods with only one parameter (these may be setters)? (undecided)
Should we disregard invocations of methods that happen in tests? (I rather think yes)
This Code Proportions Computer should discover methods that are invoked with the constant parameters
The text was updated successfully, but these errors were encountered: