Twitter | Search | |
Brandon Williams
Subterranean homesick mathematician. Working on
7,541
Tweets
553
Following
4,570
Followers
Tweets
Brandon Williams Aug 6
Replying to @SwiftyJSN @joinpursuit
Thanks for joining!
Reply Retweet Like
Brandon Williams Aug 6
No problem, thanks for having me!
Reply Retweet Like
Brandon Williams retweeted
Point-Free Aug 6
And until Combine comes with a proper way to control time in publishers, you may be interested in checking out our open source project: ⏰
Reply Retweet Like
Brandon Williams retweeted
Harshil Shah Aug 5
A while ago posted a tweet asking people what they found most difficult when learning Swift. There was only one answer for me, and so I wrote about it:
Reply Retweet Like
Brandon Williams Aug 6
This was a really well written article Harshil, thanks! It helped clear up a few things in my mind.
Reply Retweet Like
Brandon Williams Aug 5
Replying to @krzyzanowskim
There is most likely a bug in that code still. You also need to specify the other tags are of type Optional<Layer> too, otherwise it won't work. Optional promotion does not save you here:
Reply Retweet Like
Brandon Williams Aug 5
Awesome to hear Krzysztof! 😁
Reply Retweet Like
Brandon Williams Aug 3
Replying to @mecid
Awesome to hear! Glad it worked out for you 😀
Reply Retweet Like
Brandon Williams retweeted
Majid Jabrayilov Aug 1
I have finally faced a case when I need different implementations of the protocol in the same type. It is time to use protocol witnesses. If you want to learn more about this approach, take a look at the great talk by
Reply Retweet Like
Brandon Williams retweeted
Point-Free Jul 30
A popular way to design dependencies is to create a protocol with ”live“ and ”mock“ conformances. But a protocol with only two conformances is not a strong form of abstraction. Not a single protocol in the standard library has just two conformances. 👉
Reply Retweet Like
Brandon Williams retweeted
Point-Free Jul 29
We just published documentation for several of our open source projects, including the Composable Architecture 📖 Thanks to and all of the contributors, and to for the nudge!
Reply Retweet Like
Brandon Williams Jul 27
I'm very excited to start this series of episodes where we systematically break down how to properly introduce dependencies to our code without having a bunch of unknowable, untestable, black boxes of functionality littered throughout.
Reply Retweet Like
Brandon Williams Jul 23
Replying to @SergDort @mluisbrown
If you remove private(set) it will compile, and that is expected. But with private(set) it shouldn't compile. It did in beta 1 & 2, but no longer does in beta 3.
Reply Retweet Like
Brandon Williams Jul 23
This escape hatch has been closed in Xcode 12 beta 3. The argument is now marked as `inout`, which prevents you from passing in the published field:
Reply Retweet Like
Brandon Williams Jul 22
Coincidentally there is a thread on the Swift forums that demonstrates just how difficult it can be to deal with optional state in SwiftUI. Someone even shared our `unwrap` operator 😆 I've tried to provide a few responses:
Reply Retweet Like
Brandon Williams retweeted
Point-Free Jul 21
This week we looked at how an Apple deals with discardable, draft state in their "Working with UI controls" tutorial: Ideally one would use optionals to model this, but SwiftUI doesn't have to tools to do this properly, and so one must resort to hacks
Reply Retweet Like
Brandon Williams retweeted
Point-Free Jul 20
We'd love to see case paths in Swift someday! The use cases are only going to become more plentiful as time goes on.
Reply Retweet Like
Brandon Williams retweeted
Ashton Williams Jul 20
“casepaths” from continue to be mind blowing 🤯 How long until they are part of the language
Reply Retweet Like
Brandon Williams Jul 15
Replying to @Palleas
Lol mosquitos haven’t been bad yet and only internet is tethering to my phone which means it’s great for focusing 😆
Reply Retweet Like
Brandon Williams Jul 15
thanks jay jay!
Reply Retweet Like