The Swift Apple doesn't want you to know

Forbidden functions, deranged keywords, and plain weird syntax

I’ve been writing Swift daily for nearly 10 years. I’m impostor syndrome-proof. I’ve seen it all.

But every so often… I don’t know.

Maybe I make a typo in Xcode that unearths forgotten creatures from the Mariana Trench of autocomplete. Perhaps I’m buying pet chimps on the darkweb and accidentally stumble upon a blog post containing arcane syntax.

Today, we’re going to unearth some of the Swift which Apple keeps in the cupboard under the stairs. We’ll ascertain whether these keywords and functions have any real-world use cases, so we can take them out for a bit of sun.

1. unowned(unsafe)

2. withoutActuallyEscaping

3. dlopen()

4. malloc, free, and withUnsafeTemporaryAllocation

5. _modify

6. autoreleasepool

Subscribe to Jacob’s Tech Tavern for free to get ludicrously in-depth articles on iOS, Swift, tech, & indie projects in your inbox every week.

Paid subscribers get full access to this article, plus my full Quick Hacks library. You’ll also get all my long-form content 3 weeks before anyone else.

To celebrate turning 30, I’m running a 30-themed sale. Like, percentage. While paid subscribers are great, my main birthday wish is that all the other millennial parents at my son’s nursery will stop referring to me as “the really young guy”.

Not sure? How about a 2 week test-drive?