在AutoLayout中能否用Visual Format Language合并水平与垂直约束？

Great question! Let's break this down clearly:

First off, Visual Format Language (VFL) doesn’t support declaring both horizontal and vertical constraints in a single format string—each VFL line is strictly tied to one axis (either starting with H: for horizontal, or V: for vertical). So the separate calls you’re seeing are technically how VFL is designed to work, but there are absolutely ways to cut down on that redundant code.

Option 1: Combine Constraint Arrays for a Single addConstraints Call #

Instead of calling addConstraints twice, you can merge the two constraint arrays and add them in one go. This reduces method calls and cleans up the code:

// Create both constraint sets and merge them
let constraints = NSLayoutConstraint.constraints(withVisualFormat: "H:|-0-[view]-0-|", options: [], metrics: nil, views: ["view": childView])
    + NSLayoutConstraint.constraints(withVisualFormat: "V:|-0-[view]-0-|", options: [], metrics: nil, views: ["view": childView])

// Add all constraints at once
containerView.addConstraints(constraints)

Option 2: Wrap the Logic in a Reusable Extension #

If you find yourself writing this "fill superview" pattern often, create a UIView extension to encapsulate the VFL logic entirely. This turns repeated code into a single, readable method call:

extension UIView {
    func addFillingSubview(_ subview: UIView) {
        subview.translatesAutoresizingMaskIntoConstraints = false
        addSubview(subview)
        
        let constraints = NSLayoutConstraint.constraints(withVisualFormat: "H:|-0-[subview]-0-|", options: [], metrics: nil, views: ["subview": subview])
            + NSLayoutConstraint.constraints(withVisualFormat: "V:|-0-[subview]-0-|", options: [], metrics: nil, views: ["subview": subview])
        
        addConstraints(constraints)
    }
}

// Usage is now trivial:
containerView.addFillingSubview(childView)

Option 3: Ditch VFL for Modern Layout Anchors (Recommended) #

If your app targets iOS 9 or later (which is standard these days), you can replace VFL entirely with the NSLayoutAnchor API. It’s more readable, type-safe, and avoids VFL’s axis limitation:

childView.translatesAutoresizingMaskIntoConstraints = false
containerView.addSubview(childView)

// Activate all edge constraints in one call
NSLayoutConstraint.activate([
    childView.leadingAnchor.constraint(equalTo: containerView.leadingAnchor),
    childView.trailingAnchor.constraint(equalTo: containerView.trailingAnchor),
    childView.topAnchor.constraint(equalTo: containerView.topAnchor),
    childView.bottomAnchor.constraint(equalTo: containerView.bottomAnchor)
])

You can even simplify this further with a custom extension for edge alignment:

extension UIView {
    func pinEdgesToSuperview(insets: UIEdgeInsets = .zero) {
        guard let superview = superview else { return }
        translatesAutoresizingMaskIntoConstraints = false
        
        NSLayoutConstraint.activate([
            leadingAnchor.constraint(equalTo: superview.leadingAnchor, constant: insets.left),
            trailingAnchor.constraint(equalTo: superview.trailingAnchor, constant: -insets.right),
            topAnchor.constraint(equalTo: superview.topAnchor, constant: insets.top),
            bottomAnchor.constraint(equalTo: superview.bottomAnchor, constant: -insets.bottom)
        ])
    }
}

// Usage:
childView.translatesAutoresizingMaskIntoConstraints = false
containerView.addSubview(childView)
childView.pinEdgesToSuperview() // Add insets if needed, e.g., .init(top: 8, left: 8, bottom: 8, right: 8)

To recap: VFL can’t handle both axes in one string, but you don’t have to stick with the redundant two-call pattern. Merging arrays, using extensions, or switching to layout anchors will make your code cleaner and more maintainable.

内容的提问来源于stack exchange，提问作者Mark A. Donohoe