3 ms·
> std::range should stay where it is, and the new one be introduced as std::range/v2 Isn’t this what editions are for?
by metaltyphoon 5mo ago
> std::range should stay where it is, and the new one be introduced as std::range/v2
Isn’t this what editions are for?
- estebank 5mo agoYes, but no, but also yes. Editions are for language evolution. Evolving the std does fit the bill. Edition aware path resolution isn't a thing. It will likely be a thing starting with Edition 2027. Range is likely to be the first type to use this feature upcoming.
- pjmlp 5mo agoWhich is why I always give library evolution as one example why editions don't solve everything as many people think they do.
- metaltyphoon 5mo agoDon't let perfect be the enemy of good enough. This is much better, IMO, than what many other languages do, including Go's modulename/v2 style.