I should add that I have implemented some ranges where .front and
.popFront are both nothrow, as !empty doesn't "advance and cache"
for these ranges and the check is moved into an in{} contract.
For these ranges, they tend to behave like arrays with bounds
checking, only now the bounds checking is turned off by virtue of
-release.
- protocol for using InputRanges Walter Bright
- Re: protocol for using InputRanges Jakob Ovrum
- Re: protocol for using InputRanges Adam D. Ruppe
- Re: protocol for using InputRanges Rikki Cattermole
- Re: protocol for using InputRanges Jonathan M Davis
- Re: protocol for using InputRanges Joseph Rushton Wakeling
- Re: protocol for using InputRanges Marco Leise
- Re: protocol for using InputRanges w0rp
- Re: protocol for using InputRanges Szymon Gatner
- Re: protocol for using InputRanges w0rp
- Re: protocol for using InputRanges Walter Bright
- Re: protocol for using InputRanges Szymon Gatner
- Re: protocol for using InputRanges Szymon Gatner
- Re: protocol for using InputRanges Steven Schveighoffer
- Re: protocol for using InputRanges Timon Gehr
- Re: protocol for using InputRanges monarch_dodra
- Re: protocol for using InputRanges Tommi
- Re: protocol for using InputRanges Steven Schveighoffer
- Re: protocol for using InputRanges Tommi
- Re: protocol for using InputRanges Dicebot