I agreed that it looked good in the ivory tower. The thing is, there
are these real-world detractors which we should not igore. To save my
old fingers, let me just summarize them from the earlier posts. In
summary:
- it provides no known material benefit
- it could affect unsuspecting legacy application performance
materially, and in an insidious way
- it's an anomalous usage of the API which works against performance
expectations about #size and #do:.
- the justification for this change (performance optimization) in
Collection is not valid in the first place.
No real-world positives, just negatives or zeros. Please revert.