Yes and no... This is part of their standard library, so from a practical point of view, it <i>is</i> a language issue.<p>Easily? Proper implementation isn&#x27;t so trivial, look what it takes for Guava:<p><a href="https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;guava-libraries&#x2F;source&#x2F;browse&#x2F;guava&#x2F;src&#x2F;com&#x2F;google&#x2F;common&#x2F;collect&#x2F;FluentIterable.java" rel="nofollow">https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;guava-libraries&#x2F;source&#x2F;browse&#x2F;guav...</a><p><a href="https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;google-collections&#x2F;source&#x2F;browse&#x2F;trunk&#x2F;src&#x2F;com&#x2F;google&#x2F;common&#x2F;collect&#x2F;Iterables.java" rel="nofollow">https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;google-collections&#x2F;source&#x2F;browse&#x2F;t...</a><p><a href="https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;guava-libraries&#x2F;source&#x2F;browse&#x2F;guava&#x2F;src&#x2F;com&#x2F;google&#x2F;common&#x2F;collect&#x2F;Iterators.java" rel="nofollow">https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;guava-libraries&#x2F;source&#x2F;browse&#x2F;guav...</a><p>Plus:<p>* new (lazy) extension functions would be getting in the way of standard ones, you would need a paralel naming convention (perhaps one borrowed from LINQ, where map = select, filter = where, fold = aggregate and so on) and developers would still confuse one with another.<p>* unless we agree on one canonical implementation, yours would be different than mine, easy to see how it could become a mess.<p>If there is a better approach which removes these obstacles, someone let me know