Bug 8343 – Last argument of topNCopy forcing a sort?

See also Issue 8342 Currently I think topNCopy gives a heap instead of a sorted output when you give it a range that can't be sorted. In this case the last argument of topNCopy must be false (that is the default). But if the programmer gives "true" as the last argument, can't topNCopy just sort the little result calling sort() on it before returning? This way you don't have to call sort() yourself on the result if you need it truly sorted. (Please close this enhancement request if I am missing something.)

From docs : "If sorted is true, the target is sorted. Otherwise, the target respects the heap property" [1]. [1] https://dlang.org/phobos/std_algorithm_sorting.html#topNCopy > But if the programmer gives "true" as the last argument, can't topNCopy just sort the little result calling sort() on it before returning? That is exactly what it does. Closing as invalid.