使用NSLayoutAnchor创建约束，layoutMarginsGuide是否显得多余？

Great question—this is a super common point of confusion when you’re getting your feet wet with Auto Layout! Let me break down why layoutMarginsGuide isn’t redundant, even if you’ve managed to create margin-like constraints without it.

First, let’s clarify what you’re actually doing when you skip layoutMarginsGuide #

I’ll fill out your partial code example to make this concrete:

let inputsContainerView = UIView()
view.addSubview(inputsContainerView)
inputsContainerView.translatesAutoresizingMaskIntoConstraints = false

// "Manual" margin constraint you might have used
inputsContainerView.leadingAnchor.constraint(equalTo: view.leadingAnchor, constant: 8).isActive = true

What you’re doing here is hardcoding a fixed offset (8pt, the default layout margin) to simulate a margin. But this isn’t actually tied to the view’s built-in layout margins system—it’s just a static gap from the view’s edge.

What layoutMarginsGuide actually brings to the table #

layoutMarginsGuide gives you access to a UILayoutGuide that’s automatically synced with the view’s layoutMargins property. Here’s why that’s game-changing:

• Dynamic margin updates: If you ever tweak the view’s layoutMargins later (e.g., view.layoutMargins = UIEdgeInsets(top: 16, left: 16, bottom: 16, right: 16)), all constraints using layoutMarginsGuide will adjust automatically to match the new margins. Your hardcoded constant constraints won’t—you’d have to update every single one manually.
• System-adaptive behavior: iOS automatically adjusts layoutMargins in certain scenarios (like iPad split view, or when combining with safe area guides). layoutMarginsGuide respects these system adjustments out of the box, while hardcoded constants stay stuck at your chosen value.
• Cleaner, more readable code: Using inputsContainerView.leadingAnchor.constraint(equalTo: view.layoutMarginsGuide.leadingAnchor) makes your intent crystal clear—anyone reading your code immediately knows you’re aligning to the view’s layout margin, not its raw edge. No more wondering why you picked an arbitrary 8pt constant.
• No repeated boilerplate: Instead of typing constant: 8 in four separate constraints (leading, trailing, top, bottom), you set view.layoutMargins once and let the guide handle the rest.

Why UIView doesn’t have direct margin anchor properties #

You’re right that UIView doesn’t expose properties like layoutMarginLeadingAnchor directly. That’s because layout margins are a set of related insets, and UILayoutGuide is Apple’s designed way to group those anchor points (leading, trailing, top, bottom) into a single, reusable object. This keeps the UIView API clean while still giving you full access to margin-based anchors via the guide.

In short #

layoutMarginsGuide isn’t redundant—it’s the proper, maintainable way to work with layout margins in Auto Layout. Your manual constant approach works for simple throwaway cases, but it lacks the flexibility and adaptability that the guide provides for real-world, long-lived code.

内容的提问来源于stack exchange，提问作者Ninja