Drop all rows with empty slice()
calls
#6573
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This revisits a point brought up in #2252
I went to remove the early exit in
slice_rows()
and discovered it was actually being used to ensure thatslice()
with no...
returns all rows. I think this is theoretically inconsistent.I think that if we have:
then:
and:
This is inline with the logic mentioned here:
#2252 (comment)
And with these two examples:
And it allows us to remove the early exit, which to me has always been an indication that the theoretical logic is sound
"e53f5c67-a3fa-4b29-93b0-4df2710f40fa"