[Issue 8483] Definition of isOutputRange warped due to "put" implementation

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=8483

--- Comment #2 from hsteoh at quickfur.ath.cx ---
In light of recent realizations that output ranges are really only useful with
specific operations at the end of UFCS chains, such as std.algorithm.copy or
std.format.formattedWrite (and arguably, the latter could be rewritten to
return an input range instead), I'm wondering if we should just get rid of
output ranges altogether and just have .copy be the one-stop function for
implementing data sinks.

--