On Wed, Jul 17, 2013 at 09:21:08PM -0700, Jonathan M Davis wrote:
On Wednesday, July 17, 2013 17:39:19 Timothee Cour wrote:
std.range shouldn't contain public import std.array.
It's done because otherwise std.range is useless with arrays, and
arrays are probably the most frequently used
On Thursday, 18 July 2013 at 00:39:33 UTC, Timothee Cour wrote:
std.range contains public import std.array.
There are a few full module public imports like that in phobos.
What's the
rationale?
I understand for hierarchical modules (breaking modules into
packages) but
for this?
I'm pretty
Timothee Cour:
1)
html documentation should show public imports (sometimes such
public imports make sense)
2)
std.range shouldn't contain public import std.array.
Sounds good.
Bye,
bearophile
On Wednesday, July 17, 2013 17:39:19 Timothee Cour wrote:
std.range shouldn't contain public import std.array.
It's done because otherwise std.range is useless with arrays, and arrays are
probably the most frequently used type of range. We lose nothing by having
that public import. Now,
