Explore >> Select a destination
|
You are here 
|
dmtopolog.com | ||
| | | | |
swiftrocks.com
|
|
| | | | | In this article, we'll explain the concept of type erasure, how it used to be done, what's different in Swift 5.7, and how these changes work under the hood. | |
| | | | |
www.emergetools.com
|
|
| | | | | A deep dive into the Swift runtime to see how protocol conformance checks slow down post-main startup time as your binary size increases. | |
| | | | |
www.timekl.com
|
|
| | | | | Swift Generics 2: Existentials Boogaloo It's been just over two years since we first saw "Improving the UI of generics," the discussion post abo... | |
| | | | |
jmmv.dev
|
|
| | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | ||
