Exposed
Exposed copied to clipboard
preserve colection type
with
call should not change the receiver type, this is not what it is called for :)
The idea here was to return loaded entities when SizedIterable was provided. @lure , you think it's worth to return original collection for further chaining?
I believe, having the type changed is a huge disadvantage.
- It breaks the type flow, and there is no reason for it. It is
with
nottoIterableAndTransform
. - Handful of extension functions are now required to be either copy-pasted (b/c of type erasure) or go up the collection hierarchy to the point where the contract is broken.
- Note also, that while expecting the SizableIterable that type does not appear in the ext declaration.