Ranges, constantly frustrating

Jakob Ovrum jakobovrum at gmail.com
Wed Feb 12 03:08:57 PST 2014


On Wednesday, 12 February 2014 at 10:44:57 UTC, Regan Heath wrote:
> Ahh.. so this is a limitation of the range interface.  Any 
> plans to "fix" this?
>
> R

Did my original reply not arrive? It is the first reply in the 
thread...

Reproduced:

> See this pull request[1] and the linked enhancement report.
>
> Also note that calling `r.popFront()` without checking 
> `r.empty` is a program error (so it's recommended to at least 
> put in an assert).
>
> [1] https://github.com/D-Programming-Language/phobos/pull/1866


More information about the Digitalmars-d-learn mailing list