forked from OSchip/llvm-project
8111d3b89c
Summary: - when the diagnostic has an explicit range, we prefer that - if the diagnostic has a fixit, its RemoveRange is our next choice - otherwise we try to expand the diagnostic location into a whole token. (inspired by VSCode, which does this client-side when given an empty range) - if all else fails, we return the zero-width range as now. (clients react in different ways to this, highlighting a token or a char) - this includes the off-by-one fix from D40860, and borrows heavily from it Reviewers: rwols, hokein Subscribers: klimek, ilya-biryukov, cfe-commits Differential Revision: https://reviews.llvm.org/D41118 llvm-svn: 320555 |
||
|---|---|---|
| .. | ||
| authority-less-uri.test | ||
| completion.test | ||
| definitions.test | ||
| diagnostics-preamble.test | ||
| diagnostics.test | ||
| documenthighlight.test | ||
| execute-command.test | ||
| extra-flags.test | ||
| fixits.test | ||
| formatting.test | ||
| initialize-params-invalid.test | ||
| initialize-params.test | ||
| input-mirror.test | ||
| lit.local.cfg | ||
| protocol.test | ||
| rename.test | ||
| shutdown-with-exit.test | ||
| shutdown-without-exit.test | ||
| signature-help.test | ||
| too_large.test | ||
| trace.test | ||
| unsupported-method.test | ||