-
Notifications
You must be signed in to change notification settings - Fork 983
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
deregister_detector #1722
deregister_detector #1722
Conversation
This function would be helpful to de-register a detector class from the list of detectors already registered with the slither object
return on removing the first hit itself, as there can't be multiple objects of the same detector class in the _detectors.
The major issue it solves is the reusing of the same slither Object for multiple detector classes.
Thus, We are now able to re-run detectors , reusing the same slither object. We don't need to declare new slither object for each combination of detector classes. Here r1, contains results of TxOrigin , while r2 does not contain results of TxOrigin . |
It would be great to have a test case. I haven't looked into it but this might have weird effects on detector result filtering. |
Co-authored-by: alpharush <[email protected]>
Note that some detectors cache the results (ex: the reentrancies detectors), so running multiple times will not lead to a fresh run. I am not sure what is your goal with this API, but you should be aware that detectors are not side-effects free ;) |
This function would be helpful to de-register a detector class from the list of detectors already registered with the slither object.