There's no need for toSmallVector() as SmallVector.h already provides a to_vector free function that takes a range.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/lib/Conversion/PDLToPDLInterp/PDLToPDLInterp.cpp | ||
---|---|---|
385–387 | The <16> here confuses me. I think to_vector should just figure out the appropriate small-buffer capacity, the same way SmallVector itself does. I think the way to do that would be to add this diff in SmallVector.h: --- a/llvm/include/llvm/ADT/SmallVector.h +++ b/llvm/include/llvm/ADT/SmallVector.h @@ -1249,6 +1249,13 @@ to_vector(R &&Range) { return {std::begin(Range), std::end(Range)}; } +template <typename R> +SmallVector<typename std::remove_const<typename std::remove_reference< + decltype(*std::begin(std::declval<R &>()))>::type>::type> +to_vector(R &&Range) { + return {std::begin(Range), std::end(Range)}; +} + } // end namespace llvm It would be reasonable, but not strictly necessary, to then audit the codebase for places where llvm::to_vector<N>(r) is called with a template argument, and update them to call just llvm::to_vector(r). If you were to do that, presumably it'd be in a separate (and unfortunately massive) PR. |
The <16> here confuses me. I think to_vector should just figure out the appropriate small-buffer capacity, the same way SmallVector itself does. I think the way to do that would be to add this diff in SmallVector.h:
It would be reasonable, but not strictly necessary, to then audit the codebase for places where llvm::to_vector<N>(r) is called with a template argument, and update them to call just llvm::to_vector(r). If you were to do that, presumably it'd be in a separate (and unfortunately massive) PR.