Using conditional conformances to improve API ergonomics in Flint
By the magic of Swift 4 conditional conformances I managed to improve the experience when performing Flint actions when your action does not need an input or a presenter. Here’s how.
By the magic of Swift 4 conditional conformances I managed to improve the experience when performing Flint actions when your action does not need an input or a presenter. Here’s how.
Back in Spring of 2015 I started doing some work for a new release of Soundproof, my iOS app for music practice. We’d just been through launch in Autumn 2014 having gone through a rapid migration to Xcode 6 and iOS 8. The plan was to add a few little feature enhancements and push out a release.
There's a weird niche feature of Swift that lets you use didSet on local variables. I found that you can use it to hide implementation details when calling Closure blocks similar to those you would use for a Domain-Specific Language.
We're having a WWDC Keynote party in England, with free ? + ?.
The pace of change, the reliable yearly cycles, they are hard to keep up with. However I just can’t deny that iOS dev is also consistently exciting. You know there’s cool new stuff coming all the time and a world of interesting possibilities that can affect a huge number of people in the world.