"Ranges..." => "Needles..." in [starts|ends]With.
To avoid any confusion: The stuff in ranges may or may not actually be ranges. generic "Needles" is what best describes it.
Clean up endsWith unittests
Original author wrote "wrap" because filter is not bidirectional. However, the function filterBidirectional fits the need, so migrating to that.
Bit of unicode unittest in [starts|ends]With
Just sprinkling some tests. These covered a wee little bit of missing usecases.
Optimizations in startsWith
* Consolidate implementation by checking length in a single spot.
* Checks narrow string or the same types' lengths.
* Index iterates on all RA ranges (and not just Arrays).

Ends with was left untouched, because it forwards to startsWith anyways.
Optimization in startsWith(Range, Needles...)
Basically, makes it stop searching as soon as an element as matched.

This is an important optimization, that avoids a lot of startsWith's other "non-optimzations"...
Implement nextPermutation for bidirectional ranges.
Implement nextEvenPermutation.
Improve ddocs for nextPermutation and nextEvenPermutation.
Improve documentation.
Add unittests for non-default sorting order.
Fix rollover bug in nextEvenPermutation.
Add non-trivial example for nextEvenPermutation.
Oops, fix typo in ddoc.
support for non RA with length in startWith

As suggested by Andrei.

Also: More unittests
fix Issue 9199 - Module level qualified functions should be rejected

`inout` had qualified the function itself, rather than its return type.
Fixes Issue 9269 - Remove import to curl to avoid unittest build failure.
Merge pull request #1087 from 9rnsr/fix9199

Supplemental fix for Issue 9199 - Module level qualified functions should be rejected
Merge pull request #1088 from AndrejMitrovic/Fix9269

Issue 9269 - Remove import to curl to avoid unittest build failure
Fixes Issue 7142 - Implement field width for boolean formatting.
Merge pull request #1089 from AndrejMitrovic/Fix7142

Issue 7142 - Implement field width for boolean formatting