kadircet added inline comments.

================
Comment at: clang-tools-extra/clangd/XRefs.cpp:1365
   // Add the #include line to the references list.
   ReferencesResult::Reference Result;
   Result.Loc.range =
----------------
i guess this patch is not needed anymore, but one comment about this behaviour 
in clangd as well (no action needed in this patch)

why are we providing the reference to the include line itself? in other 
interactions we do that for the sake of completeness (e.g. if you trigger xrefs 
on a reference, seeing the declaration/definition location is useful) but 
usually the result under the cursor is not so interesting, especially in this 
case. the include line itself is drastically different than the nature of other 
references, the user can only see the include, if they triggered the xrefs on 
the include line itself and not when they trigger it on the symbol. also that 
ref doesn't count if there's no symbols used?

FWIW I am not sure if that's a useful interaction. What was the rationale here 
exactly? It might be useful to always emit this reference, but also append 
provider to the refs list in the other direction as well (that way the results 
will be coherent again)


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D155614/new/

https://reviews.llvm.org/D155614

_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to