H. S. Teoh 3cf78da259 [dox] Cross-reference .merge and .multiwayMerge. ... These two functions are related but play two different roles: std.algorithm.sorting.merge takes a static number of ranges of possibly disparate types (but compatible elements), and is useful for composing ranges at compile-time. However, it cannot take a variable number of ranges at runtime because all ranges must be statically known. That latter role is played std.algorithm.setops.multiwayMerge, which takes a range of ranges to merge, and so can merge a variable number of ranges at runtime. However, because of that, it cannot merge ranges of disparate types (of compatible elements), and so is unsuitable for compile-time range composition, unless a workaround like the range class interface is used. The docs for these two functions really should cross-reference each other so that users can more easily find the correct function for their needs.		2019-02-01 00:13:15 +01:00
..
comparison.d	min/max shouldn't pull std.format	2018-12-10 01:03:28 -08:00
internal.d	posix.mak: Enforce whitespace before opening parenthesis for version conditions	2018-09-22 16:57:24 +02:00
iteration.d	Fix Issue 19532 - chunkBy errors involving non-forward input ranges	2019-01-26 23:58:03 -08:00
mutation.d	Fix Issue 18913 - Cannot move static array of non-copyable type	2018-12-19 16:04:06 +02:00
package.d	Remove a few cases of underscore escaping	2018-06-04 13:05:01 +02:00
searching.d	canFind: added example to search for multiple needles in an array of hay stacks.	2018-12-11 00:44:03 -08:00
setops.d	[dox] Cross-reference .merge and .multiwayMerge.	2019-02-01 00:13:15 +01:00
sorting.d	[dox] Cross-reference .merge and .multiwayMerge.	2019-02-01 00:13:15 +01:00