How is chunkBy supposed to behave on copy

[H. S. Teoh]

On Fri, Mar 20, 2020 at 05:50:26PM -0600, Jonathan M Davis via Digitalmars-d wrote:
[...]
> And exactly what should happen with basic input ranges is not clear,
> because while ideally, you'd just require that they have full-on
> reference semantics, that tends to mean that you're forcing them to be
> allocated on the heap, which isn't really the sort of thing that we
> want to force if we can avoid it.
[...]

You could just have input ranges be a struct with the copy ctor
@disable'd, perhaps?


T

-- 
Those who've learned LaTeX swear by it. Those who are learning LaTeX swear at it. -- Pete Bleackley