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

b2.temp@gmx.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #4 from b2.temp@gmx.com ---
It looks like a failed initiative, not maintained since > 4 years.
Since summer 2016 and the initiative to put annotations on all the unittest
it's easier to locate the candidates.

--

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

hsteoh@quickfur.ath.cx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |---

--- Comment #5 from hsteoh@quickfur.ath.cx ---
There must be some misunderstanding here.  What has annotations got to do with transient ranges?

Transient ranges, as referred to in this bug, are ranges where .front may mutate once .popFront is called, thereby making it invalid for code to cache .front by assigning to a local variable and referring to the variable later after .popFront is called.  AFAIK there are no annotations that can be used for this.

Many algorithms that currently break with transient ranges actually *can* be re-implemented in a way that doesn't break, and without undue overhead. Tracking these algorithms is the purpose of this issue.

--

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

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P3

--