

However, if you use this operation in your code, then your IDE reveals its actual signature:Īs you can see, the type signature shown in the API documentation has been “simplified” Shown for the map operation does not mention CanBuildFrom: I believe this will be quite visible despite our previousĮfforts to hide CanBuildFrom from the API documentation of the collections. I think the most visible change for end-users is that transformation operationsĭon’t use CanBuildFrom anymore. Also, Stream has beenĭeprecated in favor of LazyList (see the last section). Views should behave in a more predictable way. Speaking of non-strict collections, the View type has been redesigned and Now work with non-strict collections (such as View or Stream). Is that transformation operations defined outside of the collections (like in the groupBy) and will be clearly documented.) Another benefit (Some operations, though, still eagerly evaluate Now implement custom non-strict collection types without having to worry about The good news is that the new design is more correct in the sense that you can To be overridden by non-strict collection types. Implementations were strict (they eagerly evaluated the collection elements) and had This is a change because this was not the case before. Strict collections (such as List) and non-strict collections (such as Stream).

Operations (such as map or filter) are now implemented in a way that works with both The most important change in the new collections framework is that transformation Will mention the main deprecations, the motivations behind them, and their Will introduce some new operations available in the collections. That the removal of CanBuildFrom made the API more beginner friendly. The next section presents the changes that are internal to the collections implementationīut that might have some visible impact on the surface. To catch up on the topic in a few minutes! Otherwise, this is the perfect opportunity In case you’ve thoroughly followed our previous blog posts and talks, you might Several blog articles and given several talks to explain the various changes orĬhallenges we were facing. One more article about the standard collections, really? Indeed, during the lastġ8 months a lot of work has been done on the collections side and we’ve published
