Normalize an Array

[gatesn]

This will be used prior to serialization to remove any unwanted arrays from the tree.

Should it actually just be fused with serialization?

[codspeed-hq]

Merging this PR will degrade performance by 30.46%

⚠️ 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.

⚡ 2 improved benchmarks
❌ 3 regressed benchmarks
✅ 1174 untouched benchmarks
⏩ 1323 skipped benchmarks¹

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	WallTime	u16_FoR[10M]	8 µs	9.6 µs	-16.37%
❌	WallTime	1M_50pct[500000]	57.1 µs	82.1 µs	-30.46%
❌	WallTime	1M_10pct[100000]	21 µs	29 µs	-27.44%
⚡	WallTime	u64_FoR[10M]	388.1 µs	351.3 µs	+10.47%
⚡	Simulation	chunked_bool_into_canonical[(1000, 10)]	64.1 µs	43.2 µs	+48.57%

---

_{Comparing ngates/normalize (9b78ebe) with develop (1dd2d66)}

Footnotes

1. 1323 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]

When would we use this?

[joseph-isaacs]

I am concerned that the is more of a bandaid than a fix. It will make it very easy to compress an array (include a accidental filter) and then undo it just before we serialise. I think we actually want to throw an error instead and stop the compressor adding the unwanted array in the first place