On Tue, Mar 06, 2018 at 11:20:56AM -0700, Jonathan M Davis via Digitalmars-d-announce wrote: > On Tuesday, March 06, 2018 09:41:42 H. S. Teoh via Digitalmars-d-announce > wrote: > > As they say, hindsight is always 20/20. But it wasn't so easy to > > foresee the consequences at the time when the very concept of ranges > > was still brand new. > > Except that even worse, I'd argue that hindsight really isn't 20/20. > We can see a lot of the mistakes that were made, and if we were > starting from scratch or otherwise willing to break a lot of code, we > could change stuff like the range API based on the lessons learned. > But we'd probably still screw it up, because we wouldn't have the > experience with the new API to know where it was wrong. [...]
Well, that means *hind*sight is still 20/20: we see where we went wrong, but *fore*sight is still blurry, because what we think is the solution to that wrong may not turn out to be a good solution later. :-D T -- Question authority. Don't ask why, just do it.