3 ms·
I think that people have been taking Eric example too seriously. I can't speak for him, but I doubt that Eric was suggesting that such code would be routinely w
by gpderetta 8y ago
I think that people have been taking Eric example too seriously. I can't speak for him, but I doubt that Eric was suggesting that such code would be routinely written with the range library, he was just showcasing as much as possible of the range library in as short an example as possible. In a way it was designed to maximize complexity.
These excesses have in fact a positive side: the extent that people will go to get a specific functionality (in this case lazy ranges) as a library is a signal that the feature should be part of the language.
This happened with lambdas, boost.lambda, boost.phoenix and to a lesser extent boost.bind showed that the functionality could be implemented as a library, people stated playing with it and demanded the functionality to be baked into the language.
A similar thing is happening now, there is a push to extend the proposed await syntax to become a more general (and more efficient) continuation syntax that, among other things should lead to built-in support for lazy ranges.
- alacombe 8y agoI can say that I have been guilty of writing such code, and people I worked with have too. When you are given a tool, you want to use it, especially if it gives you a lot of bell and whistle.