v1.0.0

Added

• A documentation catalog, so that the API documentation has a landing page: an overview of
  the package, and its types grouped by what they are for.

Changed

• Walking an array or a dictionary no longer retains each element to hand it over and again
  for the payload: the collection keeps its elements alive, and they are lent to be told
  apart. For collections CoreFoundation owns, an array of 16 is walked in a fifth less work
  and one of 64 in over a third less.
• Walking a dictionary of eight pairs or fewer no longer allocates: an iterator keeps the keys
  and values of a small dictionary in itself, and reads only a larger one out to the heap. For
  dictionaries CoreFoundation owns, one of 1 pair is walked in a third of the work it took and
  one of 4 in under half; none is walked in more.

Full Changelog: v0.1.0...v1.0.0

v0.1.0

Changed

• CoreFoundationValue.number, .array and .dictionary now carry views —
  CoreFoundationValue.NumberView, ArrayView and DictionaryView — in place of the
  CFNumber, CFArray and CFDictionary themselves. A view costs nothing until it is asked,
  and hands back the object it was made from as base.
• An array and a dictionary are sequences whose elements are already told apart, the way the
  collection itself was: one read by CoreFoundationValue(_:) has its elements read under the
  same guard, and a proxy among them is carried as .other. A reader no longer wraps the
  collection and tells each element apart itself.
• CoreFoundationValue.Number(_:) takes the NumberView a number is told apart as, rather
  than a CFNumber.

Removed

• CoreFoundationValue.ArrayElements and CoreFoundationValue.DictionaryElements, which
  ArrayView and DictionaryView replace. They were collections of objects not yet told
  apart, made from a CFArray or CFDictionary by hand; the views are sequences, and are
  come by only through telling an object apart.

Full Changelog: v0.0.3...v0.1.0

v0.0.3

Added

• CoreFoundationValue.Number, the value of a CFNumber as the number says it holds it: an
  Int64, a UInt64 for an integer above Int64.max, or a Double for a number of a
  floating-point type, whole or not. Number(_:) asks the questions in the order that gets
  this right, and bridges the number only when it read as negative and says it holds neither
  a signed integer nor an unsigned one. A number CoreFoundation owns is read without loss; an
  NSDecimalNumber, which says it is floating-point whatever it holds, is read as the
  nearest Double. Next to the casts that check exactness,
  an integer that is not negative is read in less than half the work, one too large for a
  tagged pointer in an eighth of it, and one above Int64.max in under a fifth.
• CoreFoundationValue.ArrayElements and CoreFoundationValue.DictionaryElements, the
  contents of a CFArray and a CFDictionary as collections of objects not yet told apart.
  Neither builds a Swift array or dictionary, a loop over either ends where the reader ends
  it, and a key that is not a string is handed over for the reader to judge. For
  collections CoreFoundation owns, walking a dictionary of 16 entries takes under a fifth of
  the work of enumerateKeysAndObjects(_:), and an array of 16 elements under a sixth of the
  work of fast enumeration; for ones bridged from Swift, under a third and under a half.

Changed

• The package no longer leaves what a number becomes and how a collection is walked to the
  reader. It tells an object apart and reads the ones that take more than a cast to read.
• The module now imports Foundation publicly.

Full Changelog: v0.0.2...v0.0.3

v0.0.2

Added

• CoreFoundationValue.typeID(of:), which answers with the CoreFoundation type ID of an object
  of unknown origin, or nil for a proxy. It is the question to ask before comparing against
  the type ID of a type that is not among the cases, such as SecKeyGetTypeID().

Full Changelog: v0.0.1...v0.0.2

v0.0.1

Added

• CoreFoundationValue, which tells a CoreFoundation object apart by its type ID: a string,
  boolean, number, data, date, array, or dictionary, or .other for an object of any other
  type. A Swift cast cannot answer this, since as? CFString succeeds for any object and
  NSNumber(value: 1) as? Bool succeeds too. Each payload is the CoreFoundation type, except
  a boolean, which is the Bool it stands for; what a number becomes and how a collection is
  walked are left to the reader.
• CoreFoundationValue(unchecked:), which reads an object that came from CoreFoundation or a
  framework built on it.
• CoreFoundationValue(_:), which reads an object of unknown origin and returns nil for a
  proxy, instead of letting CFGetTypeID send it a message it would raise on.
• Support for macOS 12, Mac Catalyst 15, iOS 15, tvOS 15, watchOS 8, and visionOS 1, with
  Swift 6.2 or later. The package is for Apple platforms alone.

Full Changelog: https://github.com/sinoru/swift-core-foundation-kit/commits/v0.0.1