mirror of
https://github.com/apple/swift.git
synced 2025-12-21 12:14:44 +01:00
4f845ccc52
For most uses, some access scopes must be "respected"--if an extended value's original lifetime originally extends beyond an access scope, its canonicalized lifetime must not end _within_ such scopes (although ending before them is fine). Currently, to be conservative, the utility applies this behavior to all access scopes. For move-only values, however, lifetimes end at final consumes without regard to access scopes. Allow this behavior to be controlled by whether or not a NonLocalAccessBlockAnalysis is provided to the utility in its constructor. rdar://104635319