diff options
| author | Kazu Hirata <kazu@google.com> | 2025-06-20 08:33:59 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-20 08:33:59 -0700 |
| commit | 887222e3526fbe08e748a33f740296ac22bf1ab1 (patch) | |
| tree | b1b696057d4b0feb314a45dd05b1651a42414170 /clang/lib/AST/ByteCode/Compiler.cpp | |
| parent | 3f1de197b1c339b311329c02bb739860b32c073f (diff) | |
| download | llvm-887222e3526fbe08e748a33f740296ac22bf1ab1.zip llvm-887222e3526fbe08e748a33f740296ac22bf1ab1.tar.gz llvm-887222e3526fbe08e748a33f740296ac22bf1ab1.tar.bz2 | |
[mlir] Migrate away from ArrayRef(std::nullopt) (NFC) (#144989)
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.
This patch takes care of the mlir side of the migration, starting with
straightforward places where I see ArrayRef or ValueRange nearby.
Note that ValueRange has a constructor that forwards arguments to an
ArrayRef constructor.
Diffstat (limited to 'clang/lib/AST/ByteCode/Compiler.cpp')
0 files changed, 0 insertions, 0 deletions