Swiftpack.co - Swift Packages by juliand665

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. - `@UserDefault` now exposes as `wasLoadedSuccessful` whether the latest load (initial or manual through `loadValue()`) succeeded, useful for migrating data to an app group. - Specified defaults suites are now actually used rather than always using `.standard` (whoops!) - Selected defaults suite is now exposed publicly. I finally found a simple way to integrate the `@UserDefault` wrapper with SwiftUI! Not sure why it took me so long, but I decided to add a lightweight wrapper to make it more ergonomic. Use `@UserDefault.State` for all your SwiftUI needs :) - Updated HandyOperators - Now compatible with tvOS and watchOS - Improvements to documentation & an actual readme - Operators now come from a package dependency rather than a file, fixing ambiguity issues when dependents had their own definitions for the same operators. This update applies the changes required and/or possible in the final release of Xcode 11 and Swift 5.1. - The key no longer has an argument label, since it'll usually be the only argument and its meaning is obvious from the context. - Default values are now provided as initial values with `=` rather than an explicit argument to the wrapper init. (Because I realized I could easily work around [the compiler crash preventing me from doing so earlier](https://bugs.swift.org/browse/SR-11059).) Use at your own risk!

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. They even take premultiplied alpha into account! Initializing pixels from not-fully-opaque `UIColor`s and `NSColor`s no longer leads to incorrect components. Everything seems to work just fine.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. - Added ways to scale rectangles up or down by floats or sizes. - Added documentation to the less trivial functions. - Turns out sizes are just scalars in 2 dimensions, so to speak. So everything can be scaled by a size now. - All types now have `map` functions that transform each component in the same way. Not quite backwards compatible, because I removed vector-vector scaling in the process. - removed several things that didn't make sense - added several things that do - breaking changes from v0.0.0; i'll stop doing those on minor releases past v1.0

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. - migrated to use SwiftPM rather than Carthage - updated to Swift 5 (oops) Need to do the annoying work of specific stats and calculations and stuff…

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. - Added an `async` version of `<-` (too bad `reasync` isn't a thing (yet?)) - Added (disfavored) overloads taking a nonmutating closure (`(T) -> Void`) for easy pointfree application of such. Turns out you also have to specify `higherThan` precedence, not just one of the two, to be well-defined. Classifying this as a bugfix. `<-` now has its own precedence group (just lower than `NilCoalescingPrecedence`) with left-associativity, so you can chain it. Unfortunately, this is technically a breaking change, so I'm incrementing the major version in accordance with semantic versioning. `<-` and `???`