On 6/6/11, Jonathan M Davis <[email protected]> wrote: > I really don't think that Andrei was thinking that people would need to save > ranges when he started internalizing all of the range types in std.range and > std.algorithm.
There are some classes like InputRangeObject defined in std.range that might be used to store a general-purpose range, but they're annotated with some comments about various bugs they have. I gave that a try a while ago, but it's a pain to make it work at all. Well.. D is a very compile-time-oriented language, as opposed to one that's focused more on runtime features. Nothing bad about that, but flexibility at runtime can be nice to have. Ranges seem to be focused on the programmer's needs, and not something you can let the user play with at runtime too much.
