Swift

How to make an Optional<T> into T when we're sure

No test facilities? Edge cases that are hard to reproduce but most apps run into? Just another day on Apple's wild ride.

uFeatures offer lower compile times, better modularity, better testability, stronger isolation, and more! Why wouldn't I use them?

It would be nice to catch fatal assertions, and magically turn all functions into throwing functions. Is it possible?

Porting an app to a uFeature architecture leads to a doubling in binary size. Why? How can we fix it?

Trying to make realtime and offline cool audio effects without ffmpeg on iOS. Did someone say undocumented C APIs? I wish they didn't!

What if you want an app with different downloaded weights for different devices?

I never ended up writing up the stable diffusion port and immensely regretted it, so this time y'alls get to hear about this odyssey of a port.

Trying to get those nice JS testing semantics in Swift

If you record all of the actions in an app, assert all of the states at every step, and record all of the side effects, you can replay the recording in a test and verify that the app behaves the same way and investigate why. This is a post about how I built a test recorder for TCA.

A post for my wandering mind during the couple frozen minutes after any file change in Xcode.

A workaround for non-nominal types that don’t conform to Equatable, but really should

When you want to inject a normal C function, things get tricky

The alternative to 'Speaker' is, apparently, 'Receiver'.

Maybe, one day, Apple will switch to using Swift and we'll see a reduction in SDK bugs.

Using runtime declarations as a feature in an otherwise strongly-typed language is not a great idea.

Hopefully this is the beginning of the end of writing Python scripts in Swift code.

A -> B -> C, but a metal file in B needs to include something from A?

A used in B used in C, but A relies on state owned by C.