On 08/16/2010 10:16 PM, David Simcha wrote:
I think that covers all the known bugs in std.range and std.algorithm,
with the following exceptions:
1. Enhancement requests, as opposed to "real" bugs.
2. Pure documentation issues.
3. Stuff related to static arrays.
4. Bug 3067, which is really a compiler bug.
This is great work!
How do we want to handle the static array case, long term? IMHO stuff in
std.range and std.algorithm should generally* not *support static arrays
because in addition to being a PITA to implement, since static arrays
are usually stack allocated, using them as ranges is inherently unsafe.
I agree. Just have people use arr[] instead of arr and call it a day.
BTW generally passing arr[] to a function where arr is a static array
allocated on the stack is an unsafe operation.
Andrei
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
