Phobos for Review: std.buffer.scopebuffer
Walter Bright
newshound2 at digitalmars.com
Sun Feb 9 16:59:04 PST 2014
On 2/9/2014 12:43 PM, Dmitry Olshansky wrote:
> 1. I guess there is a distinctive quality to a buffer (i.e. it's not just any
> output range). The current interface looks quite arbitrary - is 'pop' required
> for any buffer?
No, pop isn't required.
> A trait like isBuffer is in order, to allow user code to target
> any buffers including non-Phobos ones.
I don't understand the point of this suggestion.
> 2. May need buffer.package.d to import all common buffers (there is only one
> now, but with time...).
I do not like the idea of "kitchen sink" importing. The package.d thing was
designed so that we can split up the existing kitchen sink modules without
breaking user code.
More information about the Digitalmars-d
mailing list