[Issue 14478] isInputRange failed to recognize some ranges

[via Digitalmars-d-bugs]

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

--- Comment #9 from Peter Alexander <peter.alexander.au at gmail.com> ---
Also, I just want to say that I think this is important. The only reason we
aren't seeing its importance right now is because we have few non-copyable, but
moveable types. Barely anyone uses Unique. Once Unique becomes more popular, I
don't think we can justify a world where it's not possible to have an input
range over a container of Unique objects.

--