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
Would it be better to explicitly enumerate the "no taint propagated" methods and indicate error here if an unemumerate function is found?
I don't expect there to be much churn in the stdlib without us noticing, but it could be a good defensive measure to make sure we're not skipping over some functions without deliberately having excluded them and/or end up with a function signature that should be matching a summary but isn't due to a bug.
The text was updated successfully, but these errors were encountered:
mlevesquedion
changed the title
Determine whether we should explicitly enumerate functions that don't propagate taint
Determine how/whether we should explicitly enumerate functions that don't propagate taint
Apr 6, 2021
From @PurelyApplied on #292:
Would it be better to explicitly enumerate the "no taint propagated" methods and indicate error here if an unemumerate function is found?
I don't expect there to be much churn in the stdlib without us noticing, but it could be a good defensive measure to make sure we're not skipping over some functions without deliberately having excluded them and/or end up with a function signature that should be matching a summary but isn't due to a bug.
(Link to thread)
The text was updated successfully, but these errors were encountered: