[Issue 18807] RefRange behaves very differently for Input Ranges and Forward Ranges

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18807

Iain Buclaw  changed:

   What|Removed |Added

   Priority|P3  |P2

--


[Issue 18807] RefRange behaves very differently for Input Ranges and Forward Ranges

2018-04-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18807

--- Comment #4 from Eyal  ---
Indeed, and both are worth fixing.

So I think it makes sense to keep these 2 issues:

issue 14619 should fix compiler's foreach behavior (calling opSlice
unnecessarily)

this issue should fix RefRange in phobos, to avoid defining opSlice().

--


[Issue 18807] RefRange behaves very differently for Input Ranges and Forward Ranges

2018-04-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18807

Steven Schveighoffer  changed:

   What|Removed |Added

 CC||schvei...@yahoo.com

--- Comment #3 from Steven Schveighoffer  ---
There are 2 issues here. One is the same from 14619 -- the compiler is assuming
opSlice  on a valid range is a no-op.

The second issue is that for some reason opSlice is defined in RefRange iff
save is defined. That makes no sense.

Fixing either of these issues will fix the problem I think.

--


[Issue 18807] RefRange behaves very differently for Input Ranges and Forward Ranges

2018-04-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18807

--- Comment #2 from Eyal  ---
It's related -- but that issue is about "foreach" behavior, and this issue is
about RefRange behavior, which probably should not define opSlice (as mentioned
in passing in issue 14619).

--


[Issue 18807] RefRange behaves very differently for Input Ranges and Forward Ranges

2018-04-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18807

ag0aep6g  changed:

   What|Removed |Added

 CC||ag0ae...@gmail.com
   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=14619

--- Comment #1 from ag0aep6g  ---
Possibly a duplicate of issue 14619.

--