http://d.puremagic.com/issues/show_bug.cgi?id=10868
--- Comment #2 from Andrej Mitrovic <andrej.mitrov...@gmail.com> 2013-08-21 18:59:39 PDT --- (In reply to comment #1) > I think that we should move towards having pretty much any Phobos function > which allocates an array (including strings) have an overload which takes an > output range to write to instead. However, we should probably make sure that > output ranges are appropriately ironed out before we do that heavily (e.g. we > really need to have a clear way of asking whether an output range is full). > Input ranges are used heavily, but output ranges have had much less attention > and may need additional work before they're used that heavily. Hmm, is there any way this .full check can be added later once the output range API is finalized? For now if .put works on the buffer I think we're ok, since most buffers are likely created with appender(). If it's not in the NG already, could you bring this OutputRange topic up? We've already made a promise to make Phobos more memory-friendly (one way is providing an optional buffer), but not much has happened since the end of DConf. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
