Question 1

How to use Then with SwiftUI?

Accepted Answer

Then is not designed for SwiftUI; it works best with UIKit and NSObject subclasses. For SwiftUI, consider using view modifiers or custom initializers instead, as Then's closure-based approach doesn't align with SwiftUI's declarative model.

Question 2

Then vs manual initialization in Swift: which is better?

Accepted Answer

Then reduces boilerplate and improves readability for complex configurations, like setting up multiple UIKit properties. However, manual initialization is more transparent and dependency-free, making it preferable for simple cases or teams avoiding third-party libraries.

Question 3

How to extend a custom struct with Then?

Accepted Answer

Simply add an extension to your type conforming to the Then protocol, as shown in the README with MyType. This enables the `then()` method, allowing you to configure properties in a closure after initialization.

Question 4

Does Then have any performance impact?

Accepted Answer

Then uses standard Swift closures, so performance impact is negligible in most cases. However, there's a minor runtime overhead due to closure execution, but it's unlikely to affect app performance for typical initialization tasks.

Question 5

How to install Then without CocoaPods?

Accepted Answer

Then supports Swift Package Manager; add it as a dependency in your Package.swift file, as detailed in the README. This makes integration easy for modern Swift projects that prefer SPM over CocoaPods.

Question 6

Can Then be used with value types like arrays or dictionaries?

Accepted Answer

Yes, use the `with()` method for value types to create modified copies, as demonstrated with CGRect in the README. This works for any value type, making it versatile for data manipulation without mutating originals.

Then

What is Then?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions