Summary: Expanding traces currently works in the following way: Given a `TraceElem.Kind` `k` we want to report in `foo`, we look for a callee `C` of `foo` that has a `TraceElem.Kind` equal to `k` in its summary, grab the summary for `C`, then repeat until we bottom out. This isn't very flexible: it insists on equality between `TraceElem.Kind`'s as the criteria for expanding a trace. This diff introduces a new `matches` function for deciding when to expand a trace from a caller into a callee. Clients that don't want strict equality can implement a fuzzier kind of equality inside this function. I've gone ahead and done this for the trace elemes of thread-safety. In the near future, equivalent access paths won't always compare equal from caller to callee, so we want to match their suffixes instead. Reviewed By: jvillard Differential Revision: D5914118 fbshipit-source-id: 233c603master
parent
ca23ed5f5f
commit
983bcbbae7
Loading…
Reference in new issue