docs...
SortedRange!(Range, less) sort(alias less = "a < b", SwapStrategy
ss = SwapStrategy.unstable, Range)(Range r) if ((ss ==
SwapStrategy.unstable && (hasSwappableElements!Range ||
hasAssignableElements!Range) || ss != SwapStrategy.unstable &&
hasAssignableElements!Range) && isRandomAccessRange!Range &&
hasSlicing!Range && hasLength!Range);
vs code..
SortedRange!(Range, less)
sort(alias less = "a < b", SwapStrategy ss =
SwapStrategy.unstable,
Range)(Range r)
if (((ss == SwapStrategy.unstable &&
(hasSwappableElements!Range ||
hasAssignableElements!Range)) ||
(ss != SwapStrategy.unstable &&
hasAssignableElements!Range)) &&
isRandomAccessRange!Range &&
hasSlicing!Range &&
hasLength!Range)
Why would you make the documentation less clear than the actual
code? If somebody submitted code formatted like your docs they'd
be hung drawn and quartered.
It'd also be nice if you could click on things like SwapStrategy
and isRandomAccessRange. If you can click, read, and click back,
you can grep things so much faster than if you have to manually
look everything up.
It'd also help if there was a bit more structure conveyed in the
formating. For example the only difference between a class member
and the class is the indentation. Same font, same colours, same
underline.
