Update dependency apple/swift-collections to from: "1.3.0" #95
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/apple-swift-collections-1.x
branch
from
11aa95c to
bc1bc65
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/apple-swift-collections-1.x
branch
from
bc1bc65 to
4dbe1da
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/apple-swift-collections-1.x
branch
from
4dbe1da to
49c2ecc
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/apple-swift-collections-1.x
branch
from
49c2ecc to
426988d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/apple-swift-collections-1.x
branch
from
426988d to
03db0cf
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/apple-swift-collections-1.x
branch
from
03db0cf to
d567986
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
from: "1.0.4"->from: "1.3.0"Release Notes
apple/swift-collections (apple/swift-collections)
v1.3.0: Swift Collections 1.3.0Compare Source
This feature release supports Swift toolchain versions 6.0, 6.1 and 6.2, and it includes the following improvements:
BasicContainersmoduleThis new module collects ownership-aware, low-level variants of existing data structures in the core standard library. In this release, this module consists of two array variants,
UniqueArrayandRigidArray.These new types are provided as less flexible, noncopyable alternatives to the classic
Arraytype. The standardArrayimplements value semantics with the copy-on-write optimization; this inherently requires elements to be copyable, and it is itself copyable.struct UniqueArray<Element>is a noncopyable array variant that takes awayArray's copy-on-write behavior, enabling support for noncopyable elements. This type's noncopyability means mutations can always assume that the array is uniquely owned, with no shared copies (hence the name!). This means that array mutations such as mutating an element at an index can behave much more predictably, with no unexpected performance spikes due to having to copy shared storage.struct RigidArray<Element>goes even further, by also disabling dynamic resizing. Rigid arrays have a fixed capacity: they are initialized with room for a particular number of elements, and they never implicitly grow (nor shrink) their storage. When a rigid array's count reaches its capacity, it becomes unable to add any new items -- inserting into a full array is considered a programming error. This makes this a quite inflexible (or rigid) type indeed, as avoiding storage overflow requires careful, up front planning on the resource needs of the task at hand. In exchange, rigid arrays can have extremely predictable performance characteristics.UniqueArrayis a great default choice when a task just needs an array type that is able store noncopyable elements.RigidArrayis best reserved for use cases that require absolute, pedantic control over memory use or latency -- such as control software running in environments with extremely limited memory, or when a certain task must always be completed in some given amount of time.The
UniqueandRigidprefixes applied here establish a general naming convention for low-level variants of the classic copy-on-write data structure implementations. Future releases are expected to flesh out our zoo of container types by addingUniqueandRigidvariants of the existingSet,Dictionary,Deque,Heapand other constructs, with type names such as asRigidDictionaryandUniqueDeque.TrailingElementsModulemoduleThis new module ships a new
TrailingArrayconstruct, a preview of a new low-level, ownership-aware variant ofManagedBuffer. This is primarily intended as a interoperability helper for C constructs that consist of a fixed-size header directly followed by variable-size storage buffer.ContainersPreviewmoduleThis module is intended to contain previews of an upcoming ownership-aware container model. In this initial release, this module consists of just one construct:
struct Box<T>.Boxis a wrapper type that forms a noncopyable, heap allocated box around an arbitrary value.What's Changed
release/1.1tomainby @lorentey in #248release/1.1tomainby @lorentey in #358OrderedSet.appending(contentsOf:)by @pm-dev in #452SortedCollectionsmodule by @lorentey in #479release/1.2tomainbranch by @lorentey in #487release/1.2by @cthielen in #498pull_request.ymlby @MaxDesiatov in #509Box,RigidArray,DynamicArrayby @lorentey in #508archsub-folder by @Steelskin in #505New Contributors
Full Changelog: apple/swift-collections@1.2.1...1.3.0
v1.2.1: Swift Collections 1.2.1Compare Source
This is a patch release with the following minor improvements:
BigStringsometimes miscounted distances in its character view, resulting in an invalid collection conformance. This is now fixed. (#485)BigString's Unicode Scalar and character views now make better use of known lengths of the text chunks stored in the tree, resulting in significantly improved performance for their distance measurements. (#486)What's Changed
Full Changelog: apple/swift-collections@1.2.0...1.2.1
v1.2.0: Swift Collections 1.2.0Compare Source
This feature release includes the following improvements:
Heap.removeAll(where:)(#454)OrderedSet.appending(contentsOf:)(#452)Heapoperations now agree on the identity of the maximal element, even if it has duplicates (#439)OrderedSetnow runs faster in unspecialized generic contexts (#433)ManagedBuffer.capacity(#456)This version supports Swift toolchain versions 5.10, 6.0 and 6.1.
What's Changed
OrderedSet.initandOrderedSet.firstIndex(of:)by @dnadoba in #433_specialize(_:for:)for the 5.9 stdlib by @lorentey in #472String.Index._descriptionby @lorentey in #474New Contributors
Full Changelog: apple/swift-collections@1.1.4...1.2.0
v1.1.6: Swift Collections 1.1.6Compare Source
This is a patch release updating the CMake build configuration that is used to build Swift toolchains. There were no changes to the package.
What's Changed
Full Changelog: apple/swift-collections@1.1.5...1.1.6
v1.1.5: Swift Collections 1.1.5Compare Source
This is a patch release updating the CMake build configuration that is used to build Swift toolchains. There were no changes to the package.
What's Changed
Full Changelog: apple/swift-collections@1.1.4...1.1.5
v1.1.4: Swift Collections 1.1.4Compare Source
This patch release consists of changes to the (unstable) CMake configuration. It includes no code level modifications.
This is expected to be the last planned release in the 1.1 release series. The next tagged release will be 1.2.0, bumping the required Swift toolchain to 5.9.
What's Changed
SWIFT_SYSTEM_NAMErather than just lowercasing. by @al45tair in #421New Contributors
Full Changelog: apple/swift-collections@1.1.3...1.1.4
v1.1.3: Swift Collections 1.1.3Compare Source
This patch release ships bug fixes for issues discovered since 1.1.2.
What's Changed
BigString.initby @lorentey in #405New Contributors
Full Changelog: apple/swift-collections@1.1.2...1.1.3
v1.1.2: Swift Collections 1.1.2Compare Source
This patch release updates the (unstable) CMake build configuration to support the swift-foundation project.
There were no changes outside of the CMake configuration.
What's Changed
Full Changelog: apple/swift-collections@1.1.1...1.1.2
v1.1.1: Swift Collections 1.1.1Compare Source
This patch release resolves issues uncovered since version 1.1.0 was published.
What's Changed
Dequethat can cause incorrect runtime traps in debug builds. (#381)_CollectionsUtilitieswas renamed toInternalCollectionsUtilitiesto work around an issue in shipping versions of Xcode. This renaming is not intended to make this module public -- it remains an unstable implementation detail. (#364)New Contributors
Many thanks to our contributors for their work!
List of Pull Requests
Full Changelog: apple/swift-collections@1.1.0...1.1.1
v1.1.0: Swift Collections 1.1.0Compare Source
This feature release adds a number of new data structure implementations, along with minor changes to existing constructs.
New Data Structures
Heapimplements a min-max heap, backed by a native array. (Contributed by @AquaGeek)BitSetandBitArrayare two alternate representations of a bitmap type, backed by dynamically allocated storage. (Contributed by @MahanazAtiqullah)TreeSetandTreeDictionaryare hashed collections implementing Compressed Hash-Array Mapped Prefix Trees (CHAMP). They provide similar API asSet/Dictionaryin the Standard Library, but as persistent data structures, supporting incremental mutations of shared instances and efficient structural diffing. (Contributed by @msteindorfer)Other Changes
OrderedSet.isEqualSetfamily of functions provide a way to test that two containers contain the same members, ignoring the order of elements. (#183, #234)OrderedSet.filterimplements a version of the standard filter operation that returns anOrderedSetinstead of anArray. (#159)debugDescriptionimplementations have been updated to follow Swift best practice. (These are called by container types likeArrayto print their elements, so they work best when they're succinct variants ofdescriptionthat are suitable for embedding in structured output: specifically, they must not produce unpaired delimiter characters ([/],(/),{/},</>etc), raw top level commas, semicolons, colons, unquoted strings etc.debugDescriptionshould not needlessly print type names etc.)New Contributors
Many thanks to our contributors for their great work (and patience)!
List of Pull Requests
Full Changelog: apple/swift-collections@1.0.6...1.1.0
subscript(offset:)for now by @lorentey in #92release/1.0intomainby @lorentey in #108Heaphasn't been tagged yet & list other enhancements in progress by @lorentey in #109import Foundationby @compnerd in #118ascendinganddescendingviews by @lorentey in #119release/1.0tomainby @lorentey in #141PersistentSetby @lorentey in #193PriorityQueueModuletoHeapModuleby @lorentey in #194mutatingkeywords by @lorentey in #238ShareabletoTreeby @lorentey in #242Sendableconformance by @lorentey in #271selfdoesn’t get destroyed before we’re done working with it by @lorentey in #276Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.