On Fri, Nov 14, 2014 at 10:22:16PM +0000, Brad Anderson via Digitalmars-d 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
OTOH, the current std.range also has a lot of other "adapters" like cycle, take, etc.. Which you probably don't want to be importing every time just because you need to use array range primitives. T -- First Rule of History: History doesn't repeat itself -- historians merely repeat each other.
