Why Extensions with constraints in Swift? - Purpose & Use Cases

The Big Idea

What if you could write one piece of code that magically works only where it should, without extra effort?

The Scenario

Imagine you have many different types in your Swift app, like arrays, strings, or custom objects. You want to add a new feature only to those types that can be compared or have certain properties. Doing this manually means writing the same code again and again for each type.

The Problem

Writing separate code for each type is slow and boring. It's easy to make mistakes or forget to update one place. Also, your code becomes messy and hard to maintain because you repeat yourself a lot.

The Solution

Extensions with constraints let you add new features only to types that meet certain rules. This means you write the code once, and Swift automatically applies it only where it makes sense. It keeps your code clean, safe, and easy to update.

Before vs After

✗ Before

extension Array { func compareAll() { /* code for arrays */ } } extension Set { func compareAll() { /* code for sets */ } }

✓ After

extension Collection where Element: Comparable { func compareAll() { /* shared code for all comparable collections */ } }

What It Enables

You can write smarter, reusable code that works only for the right types, saving time and avoiding bugs.

Real Life Example

Suppose you want to sort any collection of items that can be compared, like a list of names or scores. Using extensions with constraints, you add sorting once, and it works everywhere it should.

Key Takeaways

Manual repetition is slow and error-prone.

Extensions with constraints add code only to suitable types.

This keeps code clean, reusable, and safe.