Details
Diff Detail
- Repository
- rCTE Clang Tools Extra
Event Timeline
Technically this is NFC, but it has a huge toString helper and I'm not sure if I chose the appropriate place for logging the filename.
This looks really useful! Main suggestion is to drop the added span and attach kind to the main span instead. (It's relevant to index too, not just to sema)
clangd/CodeComplete.cpp | ||
---|---|---|
429 | hmm, this really looks like it belongs next to CodeCompletionContext::Kind? | |
453 | I think this span is going to be tiny (hard to see in some UIs!) and generally not add a lot of value itself. My instinct is that the #items can be dropped entirely - we already log the number of items from Sema considered (before Limit) so all we'd be losing is the number hidden/ineligible/destructor completions we drop here, which seems uninteresting for tracing purposes. | |
454 | sema_results_prefilter? | |
867 | FWIW, I have a (delayed, sorry) patch to add a span to all actions run by TUscheduler, which would log the filename. If that lands, *maybe* we don't want it in both places (it'd be the parent span of this one)? But not sure. |
- Attach completion kind in CodeCompleteFlow::run().
- Move printCompletionKind closer to CompletionContext::Kind.
- Added FIXME to remove tracing of filename.
- Rename usage of printCompletionKind to getCompletionKindString
- Remove tracing of the filename, TUScheduler now provides those traces
hmm, this really looks like it belongs next to CodeCompletionContext::Kind?