aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/BitcodeReader.cpp
diff options
context:
space:
mode:
authorEbuka Ezike <yerimyah1@gmail.com>2025-05-06 13:41:45 +0100
committerGitHub <noreply@github.com>2025-05-06 13:41:45 +0100
commite8adb3add5d7043178045b2235e32efbec5d6419 (patch)
tree030a53ed3b0e9a4fb698ef91baae10e92518ab4a /llvm/lib/Bitcode/Reader/BitcodeReader.cpp
parent027b2038140f309467585298f9cb10d6b37411e7 (diff)
downloadllvm-e8adb3add5d7043178045b2235e32efbec5d6419.zip
llvm-e8adb3add5d7043178045b2235e32efbec5d6419.tar.gz
llvm-e8adb3add5d7043178045b2235e32efbec5d6419.tar.bz2
[lldb][lldb-dap] use the new protocol for setVariable requests. (#137803)
```cpp // The "id" is the unique integer ID that is unique within the enclosing // variablesReference. It is optionally added to any "interface Variable" // objects to uniquely identify a variable within an enclosing // variablesReference. It helps to disambiguate between two variables that // have the same name within the same scope since the "setVariables" request // only specifies the variable reference of the enclosing scope/variable, and // the name of the variable. We could have two shadowed variables with the // same name in "Locals" or "Globals". In our case the "id" absolute index // of the variable within the dap.variables list. const auto id_value = GetInteger<uint64_t>(arguments, "id").value_or(UINT64_MAX); if (id_value != UINT64_MAX) { ``` I dropped this part because. variables that have the same name has a ` @path` suffix on both of them. and the setVariableArguments does not have a field called `id`.
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions