HomePhabricator

Second attempt to add iterator_range::empty()

Authored by jordan_rose on Oct 7 2019, 11:14 AM.

Description

Second attempt to add iterator_range::empty()

Doing this makes MSVC complain that empty(someRange) could refer to
either C++17's std::empty or LLVM's llvm::empty, which previously we
avoided via SFINAE because std::empty is defined in terms of an empty
member rather than begin and end. So, switch callers over to the new
method as it is added.

https://reviews.llvm.org/D68439

llvm-svn: 373935

Details

Committed
jordan_roseOct 7 2019, 11:14 AM
Parents
rGf385a3814047: [libc++abi] Remove redundant link flags on Apple platforms
Branches
Unknown
Tags
Unknown