Support runend canonicalization for lists

[danking]

Summary

• add list dtype support in run_end_canonicalize via run index expansion and the existing take path
• cover list(i64), list(bool), and list(utf8) run-end canonicalization

Tests

• cargo test -p vortex-runend test_runend_list -- --nocapture
• cargo test -p vortex-runend
• cargo clippy -p vortex-runend --all-targets --all-features
• cargo +nightly fmt --all

[codspeed-hq]

Merging this PR will regress 1 benchmark

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 6 improved benchmarks
❌ 1 regressed benchmark
✅ 2174 untouched benchmarks
⏩ 206 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	random_i8[0.8]	68.9 µs	98.2 µs	-29.86%
⚡	Simulation	random_i16[0.8]	92.1 µs	74 µs	+24.45%
⚡	WallTime	words_gather_scalar_avx2[65536]	9.3 µs	8.2 µs	+13.49%
⚡	Simulation	allocate_drop_arrow[0]	456.9 ns	402.7 ns	+13.45%
⚡	Simulation	allocate_drop_bytes[0]	520.2 ns	466 ns	+11.62%
⚡	WallTime	mul_i32_nonnull_avx512	7.9 µs	7.1 µs	+11.59%
⚡	WallTime	mul_u32_nonnull_avx512	6.3 µs	5.7 µs	+10.61%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing dk/runend-list-canonicalize (d7ddd10) with develop (dab1684)}

Footnotes

1. 206 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[joseph-isaacs]

i guess you could leave the validity as a run end array?

[danking]

@joseph-isaacs I actually wanted to ask you about that!

Would it be copacetic to simply recreate three RunEndArray's for the offsets, the sizes, and the validity? Or is that not what this method is supposed to do?

[danking]

I changed it to just push the RunEnd into the offsets, sizes, and validity.

[joseph-isaacs]

I wonder if its worth fusing these two decode, seem like it will be much faster?

[danking]

this is now made irrelevant though this is still an interesting question.