BTree v3.0.0 Release Notes

Release Date: 2016-09-24 // about 5 years ago
  • ๐Ÿš€ This release of BTree provides support for Swift 3.0, which involves extensive breaking API changes.

    • ๐Ÿ‘€ All API names have been reviewed and renamed to follow current Swift guidelines. (See SE-0023, [SE-0005][se0005], SE-0006, SE-0118, and possibly others.) The resulting changes are too numerous to list here. Unfortunately, resource constraints prevented me from including forwarding availability declarations for renamed APIs; fixits won't be available, you'll have to rename usages in your code by hand. (Sorry about that.)
    • BTree's collection types now implement the new collection model described in [SE-0065][se0065]. BTreeIndex has been stripped of its public methods; use the new index manipulation methods in the various collection types instead. The underlying implementation hasn't been changed, but making the standalone index methods internal now allows for experimentation with more efficient indices without breaking API changes in the future.
    • โ†ช OrderedSet was renamed to SortedSet, to prevent confusion with the similar class in Foundation. For a short while, SE-0086 renamed NSOrderedSet to OrderedSet in the Foundation framework, leading to a naming conflict with BTree. This was further aggravated by a naming lookup issue in the language itself that made it impossible to use the explicit name BTree.OrderedSet to work around the conflict. NSOrderedSet was quickly changed back to its original name, but the issue revealed that the two names are much too similar.
    • SortedSet was adapted to implement the new SetAlgebra protocol in [SE-0059][se0059].
    • Lists that contain objects now have an arrayView property that returns an NSArray with the exact same values as the List in O(1) time. This is useful for using B-tree based lists in APIs that need arrays, without copying elements. (For example, you can now use NSCoder to encode Lists directly.)
    • Collection protocol conformance has been improved. List now explicitly conforms to RandomAccessCollection, while Map and SortedSet are now BidirectionalCollections. This required no major changes as these types already implemented everything that was necessary for conformance to these stricter protocols, but now conformance is made explicit.

    ๐ŸŒ [se0005]:

    โšก๏ธ [se0059]: ๐Ÿšš [se0065]: