d-enk c70160efcd fix: correct DropByIndex handling of negative indices out of bounds (#778) ...

Fixed DropByIndex function for the case when a negative index exceeds
the slice size. This caused subsequent indices to have incorrect
offsets, leading to incorrect results.

Example of the bug:
  DropByIndex([]int{0, 1, 2, 3, 4}, -100, 4)
  returned []int{0, 1, 2, 4} instead of []int{0, 1, 2, 3}

Improvements:
- Removed map-based uniqueness check, now uses sorted iteration with O(1) memory
- Added copy of indexes to prevent mutation of input
- Fixed negative index handling logic
- Improved range check using uint for proper bounds validation

Performance:
- Time: -75.61% (geomean)
- Memory: -62.65% (geomean)
- Allocations: -43.67% (geomean)

Additional:
- Optimized Filter and FilterI in mutable/slice.go

2026-02-22 04:27:07 +01:00

..

slice_example_test.go

lint: enable gofumpt extra rules (#690)

2025-09-26 13:32:59 +02:00

slice_test.go

lint: enable gofumpt extra rules (#690)

2025-09-26 13:32:59 +02:00

slice.go

fix: correct DropByIndex handling of negative indices out of bounds (#778)

2026-02-22 04:27:07 +01:00