aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite
diff options
context:
space:
mode:
authorKazu Hirata <kazu@google.com>2025-06-22 06:30:17 -0700
committerGitHub <noreply@github.com>2025-06-22 06:30:17 -0700
commitdec93ae45492cd84e3eec05f00ffb0fb1d35f045 (patch)
treedf7e5957db3b081fa595fa3a708318811a604336 /lldb/packages/Python/lldbsuite
parent2ac293f5ac4cf65c0c038bf75a88f1d6715e467d (diff)
downloadllvm-dec93ae45492cd84e3eec05f00ffb0fb1d35f045.zip
llvm-dec93ae45492cd84e3eec05f00ffb0fb1d35f045.tar.gz
llvm-dec93ae45492cd84e3eec05f00ffb0fb1d35f045.tar.bz2
[mlir] Migrate away from ValueRange(std::nullopt) (NFC) (#145210)
ArrayRef has a constructor that accepts std::nullopt. This constructor dates back to the days when we still had llvm::Optional. Since the use of std::nullopt outside the context of std::optional is kind of abuse and not intuitive to new comers, I would like to move away from the constructor and eventually remove it. One of the common uses of std::nullopt is in one of the constructors for ValueRange. This patch takes care of the migration where we need ValueRange() to facilitate perfect forwarding. Note that {} would be ambiguous for perfecting forwarding to work.
Diffstat (limited to 'lldb/packages/Python/lldbsuite')
0 files changed, 0 insertions, 0 deletions