[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sarif] More threadFlowLocation.kind values
I was wondering in general why we changed our mind regarding the kind property (looks like I missed the discussion) – if I recall correctly, at the face-to-face meeting we agreed not to use this property.
Bu since we are working on the list, I am curious about why we have ‘sanitizer’ kind on the list, considering it will probably not be part of any result (result won’t be generated in this case). Or is the idea that it might be part of some informational result? On the other hand, why not add a ‘passthrough’ kind to indicate that the taint was propagated at this location. Also, what about something like ‘endScope’ to indicate the end of the variable scope? Finally, do we need a separate kind for lambda?
I’d suggest making the first two concepts more generic. Entry points may occur at the driver or dynamic linked library level, for example, for some checkers. The following names might help make these a bit more general purpose
‘terminate’ might be another option.
He requested some additional values:
Remember, the list is not meant to be exhaustive. The spec explicitly permits you to use any value you want if the defined values don’t meet your needs.