Replace std:: algorithms taking begin/end iterators with llvm:: counterparts
accepting ranges.
Details
Details
- Reviewers
rafauler maksfb - Commits
- rGd2c876993625: [BOLT][NFC] Use range-based STL wrappers
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
It's a bit confusing to call a function named "stable_sort", which is a well-known C++ stdlib function, but we're actually calling stable_sort from LLVM and not from stdlib. I've tried looking up in LLVM repo and there are all sorts of usages of is_contained, for example: some of them use llvm:is_contained, others use is_contained directly. What is your take on this? Should we call llvm::stable_sort, or just stable_sort?