Bug 10173 – std.algorithm.remove should throw exception on wrong ordering of indices to remove

The following passage from documentation is not respected: """ Multiple indices can be passed into remove. In that case, elements at the respective indices are all removed. The indices must be passed in increasing order, otherwise an exception occurs. """ The following test asserts in remove for all 4 cases (r1-r4): unittest { import std.algorithm, std.range, std.stdio, std.typecons; int[] test = iota(0, 10).array; auto r1 = remove!(SwapStrategy.stable)(test, tuple(2, 4), tuple(1, 3)); auto r2 = remove!(SwapStrategy.unstable)(test, tuple(2, 4), tuple(1, 3)); auto r3 = remove!(SwapStrategy.stable)(test, 2, 4, 1, 3); auto r4 = remove!(SwapStrategy.unstable)(test, 2, 4, 1, 3); } Better yet remove may as well do reordering and merging of overlaping regions. Depending on how this is solved it could become an enhancement request. But at the very least Docs and code must be in sync.

Andrei's pull has been merged; has it solved this issue, or is there still more to be addressed?

Hmm, nevermind, just tested on git HEAD, it still asserts.

It's fixed now, isn't it ?