diff options
| author | Walter Erquinigo <a20012251@gmail.com> | 2024-01-02 13:06:13 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-02 13:06:13 -0500 |
| commit | ffd173ba0b4a6d84f45308e78cea4af611bec10e (patch) | |
| tree | 9592f5344b63cbd769e4eaf7f7a3022141fb9bde /llvm/lib/Object/WasmObjectFile.cpp | |
| parent | 71f8ea3062a6b0a190835853ee77e58469763b9e (diff) | |
| download | llvm-ffd173ba0b4a6d84f45308e78cea4af611bec10e.zip llvm-ffd173ba0b4a6d84f45308e78cea4af611bec10e.tar.gz llvm-ffd173ba0b4a6d84f45308e78cea4af611bec10e.tar.bz2 | |
[lldb-dap] Emit more structured info along with variables (#75244)
In order to allow smarter vscode extensions, it's useful to send
additional structured information of SBValues to the client.
Specifically, I'm now sending error, summary, autoSummary and
inMemoryValue in addition to the existing properties being sent. This is
cheap because these properties have to be calculated anyway to generate
the display value of the variable, but they are now available for
extensions to better analyze variables. For example, if the error field
is not present, the extension might be able to provide cool features,
and the current way to do that is to look for the `"<error: "` prefix,
which is error-prone.
This also incorporates a tiny feedback from
https://github.com/llvm/llvm-project/pull/74865#issuecomment-1850695477
Diffstat (limited to 'llvm/lib/Object/WasmObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions