Releases: apple/swift-collections-benchmark
0.0.3
This is a minor maintenance release fixing filename-related issues on Windows systems and bumping dependencies to the latest stable versions.
Pull requests
- #9 Make Paths Windows‐Compatible (by @SDGGiesbrecht)
- #10 [library render]: Sanitize generated filenames (by @lorentey)
- #13 Correct benchmark typo (by @mdznr)
- #14 Bring dependencies to source-stable versions (by @WowbaggersLiquidLunch)
- #16 Bump dependencies to latest revisions (by @lorentey)
Full patch: 0.0.2...0.0.3
Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package.
0.0.2
Additions
- The package now comes with a sample benchmark in the
Documentation/Example
directory. (#6)
Fixes
- Swift Collections Benchmark now works more reliably on platforms with lower resolution timers (#4)
- Resolved a build issue when building the package on iOS, watchOS and tvOS platforms. (#5)
Source incompatible changes
Note: Existing benchmark definitions created for 0.0.1 will continue to work without changes in this release.
The package is no longer using CGFloat
, CGPoint
, CGSize
, CGRect
and AffineTransform
in its public API; these types have been replaced with Double
, Point
, Vector
, Rectangle
and Transform
, respectively. This change only affects the charting APIs (including option structs such as Theme
); it doesn't affect benchmark definitions. (We also kept serialization formats compatible with the 0.0.1 release.)
The BenchmarkResults.Point
type has been renamed Measurement
, with a deprecated typealias put in place for the original name.
Pull requests
(You can also find a full list of issues resolved and PRs merged in this release by looking at the 0.0.2 milestone.)
- #2: Update README.md (by @stephencelis)
- #3: [Timer] Round zero measurements to the resolution of the timer (by @lorentey)
- #6: Example for docs (by @heckj)
- #8: Stop using CG types outside renderers (by @lorentey)
Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package.