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
an operator like operator <<(Stream x) would become |cpp+method://bla/operator%20%20%3C%3C...| because there are accidentally two spaces between operator and <<, while at the resolution of a usage site the name would not contain the spaces. This way we miss links between declarations and usages of operators in the call graph and we have false negatives in the downstream analyses.
The text was updated successfully, but these errors were encountered:
yes that would definitely work, but then we would never observe any hidden other issues anymore. So I prefer a more "surgical" approach. I'll do exactly that, but only if the resolved method name is an operator.
an operator like
operator <<(Stream x)
would become|cpp+method://bla/operator%20%20%3C%3C...|
because there are accidentally two spaces betweenoperator
and<<
, while at the resolution of a usage site the name would not contain the spaces. This way we miss links between declarations and usages of operators in the call graph and we have false negatives in the downstream analyses.The text was updated successfully, but these errors were encountered: