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

https://issues.dlang.org/show_bug.cgi?id=8483 Iain Buclaw changed: What|Removed |Added Priority|P2 |P3 --

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

https://issues.dlang.org/show_bug.cgi?id=8483 --- Comment #10 from hst...@quickfur.ath.cx --- Would it make sense to extend the definition of output range to include a .full method? --

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

https://issues.dlang.org/show_bug.cgi?id=8483 --- Comment #9 from Jonathan M Davis --- (In reply to monarchdodra from comment #7) > 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 coul

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

https://issues.dlang.org/show_bug.cgi?id=8483 yebblies changed: What|Removed |Added CC||yebbl...@gmail.com --- Comment #8 from yebblies -

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

https://issues.dlang.org/show_bug.cgi?id=8483 --- Comment #7 from monarchdo...@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 co

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

https://issues.dlang.org/show_bug.cgi?id=8483 --- Comment #6 from Jonathan M Davis --- H. Well, that's certainly food for thought. Output ranges are definitely for when you're writing out the final output, not for composability. However, in many of the cases where an output range would be use

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

https://issues.dlang.org/show_bug.cgi?id=8483 --- Comment #5 from hst...@quickfur.ath.cx --- I didn't say anything was *flawed* with output ranges. I just said that they are not *as* useful because, being sinks, any code that uses them will terminate the processing chain, making it non-composable

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

https://issues.dlang.org/show_bug.cgi?id=8483 Jonathan M Davis changed: What|Removed |Added CC||jmdavisp...@gmx.com --- Comment #4 from Jo

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

https://issues.dlang.org/show_bug.cgi?id=8483 --- Comment #3 from monarchdo...@gmail.com --- (In reply to hsteoh from comment #2) > 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.fo

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

https://issues.dlang.org/show_bug.cgi?id=8483 --- Comment #2 from hst...@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 latt

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

https://issues.dlang.org/show_bug.cgi?id=8483 hst...@quickfur.ath.cx changed: What|Removed |Added CC||hst...@quickfur.ath.cx --