I agree that we can't keep yanking stuff with no warning and yet call
Phobos2 production ready.
David Simcha wrote:
Speaking of sortedRange, I think we need to put lowerBound, upperBound
and canFindSorted back in std.algorithm, but make them scheduled for
deprecation. I was actually using these and a bunch of my code broke.
In general, I don't think we need to be anal about backwards
compatibility in Phobos yet, but I think that when things are removed
they should always be scheduled for deprecation for a few releases,
then deprecated for a few releases, never removed without any warning
whatsoever.
On Wed, Sep 15, 2010 at 1:31 PM, Rainer Schuetze <[email protected]
<mailto:[email protected]>> wrote:
I've hit a bad assertion in the new std.range.SortedRange:
immutable size_t msb = bsr(this._input.length) + 1;
assert(msb > 0 && msb < this._input.length);
fails for length 2.
_______________________________________________
dmd-beta mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/dmd-beta
