On Friday, 14 November 2014 at 22:22:17 UTC, Brad Anderson wrote:
On Friday, 14 November 2014 at 21:52:04 UTC, David Nadlinger
wrote:
On Friday, 14 November 2014 at 06:10:43 UTC, Rikki Cattermole
wrote:
std.range.checks
For this, std.range.constraints would also be perfectly fine.
The point is that the module also contains the array->range
adapters that are definitely not constraints, checks, or
however else you might call them.
David
Perhaps they shouldn't be in the same module then.
Maybe use two submodules:
std.range.checks (or constraints)
std.range.adapters
As far as I understand idea is exactly to separate it (while
release has not happened and it is not too late)
