diff options
author | Arthur O'Dwyer <arthur.j.odwyer@gmail.com> | 2021-12-13 19:21:38 -0500 |
---|---|---|
committer | Arthur O'Dwyer <arthur.j.odwyer@gmail.com> | 2021-12-22 12:29:42 -0500 |
commit | cb8a0b07974eb6a6aa681c30ce694e13b33a3db5 (patch) | |
tree | b1c052930f3dc08be368aed049dd358e7a54461d /mlir | |
parent | 4a10457d33e92f2e024f6d024d168ddcd49c3a59 (diff) | |
download | llvm-cb8a0b07974eb6a6aa681c30ce694e13b33a3db5.zip llvm-cb8a0b07974eb6a6aa681c30ce694e13b33a3db5.tar.gz llvm-cb8a0b07974eb6a6aa681c30ce694e13b33a3db5.tar.bz2 |
[libc++] [ranges] Introduce _LIBCPP_AUTO_CAST(x) for auto(x).
Clang is gaining `auto(x)` support in D113393; sadly there
seems to be no feature-test macro for it. Zhihao is opening
a core issue for that macro.
Use `_LIBCPP_AUTO_CAST` where C++20 specifies we should use `auto(x)`;
stop using `__decay_copy(x)` in those places.
In fact, remove `__decay_copy` entirely. As of C++20, it's purely
a paper specification tool signifying "Return just `x`, but it was
perfect-forwarded, so we understand you're going to have to call
its move-constructor sometimes." I believe there's no reason we'd
ever need to do its operation explicitly in code.
This heisenbugs away a test failure on MinGW; see D112214.
Differential Revision: https://reviews.llvm.org/D115686
Diffstat (limited to 'mlir')
0 files changed, 0 insertions, 0 deletions