You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vector_selection.cc contains multiple kernel implementations — take, filter, drop_null... — and many specializations. It's hard to see what is related to what and if we mix in kernel specializations for run-end encoded filters and data it will get really hard to review for completeness
Component(s)
C++
The text was updated successfully, but these errors were encountered:
…#35751)
### Rationale for this change
When working on #35001 I had a hard time figuring where to place the code for all possible combinations of filters and REE data. `vector_selection.cc` is hard to follow with so many kernels implemented in a single file. This PR splits the two biggest ones: filter and take. Stuff that can be shared by both stays is in `vector_selection_internal.cc` and `vector_selection.cc` is concerned with the registering of the functions and a few smaller kernels.
### What changes are included in this PR?
- [x] `vector_selection_(internal|take|filter).(cc|h)` source files were extracted from `vector_selection.cc`
### Are these changes tested?
Yes, by existing tests.
* Closes: #35765
Authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>
Signed-off-by: Antoine Pitrou <antoine@python.org>
Describe the enhancement requested
vector_selection.cc
contains multiple kernel implementations —take
,filter
,drop_null
... — and many specializations. It's hard to see what is related to what and if we mix in kernel specializations for run-end encoded filters and data it will get really hard to review for completenessComponent(s)
C++
The text was updated successfully, but these errors were encountered: