Hello SwiftUI team,
When building custom container layouts conforming to the Layout protocol that dynamically flow content around the new .division reserved region (avoiding the fold area), what is the expected performance contract during rapid physical hinge movement?
Does the continuous hinge motion invalidate the layout cache (makeCache / updateCache) on every frame, or are intermediate hinge angles decoupled from container re-measurements (sizeThatFits) to prevent layout thrashing?
For asymmetric safe areas across the inner dual-pane presentation, what is the canonical way for a custom Layout to read the reserved division bounds directly from LayoutSubviews / subview.layoutPriority, without having to wrap each subview in a GeometryReader or an explicit ArrangementView that could disrupt matchedGeometryEffect transitions across the fold?
Thanks!