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

[via Digitalmars-d-bugs]

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

--- Comment #7 from monarchdodra at gmail.com ---
In a nutshell, I have issues with an input range being able to be an output
range, because there is no way to determine if it is "full".

Heck, even if we could, I resent the notion that an output range could be
"full" at all!

Honestly, I wish we had never mixed the notion of (Input)Ranges with output
ranges. IMO, we should have had:
-InputRange
-InputRange && hasAssignableElements (writeable output ranges)
-Sinks (like "writeln", or "container.put")

And to be honest, I've almost never seen anyone use the OutputRange interface
on an input Range. The only case I know of is "copy". And I don't think it
should.

--