Erik Eckstein 78e171303c Swift AccessUtils: improve ergonomics of getAccessPathWithScope ...

It doesn't make sense to let getAccessPathWithScope return an `EnclosingScope` as the second tuple element, because in case it's a `base`, it duplicates the `AccessBase` (which is returned in the first tuple element).
Instead just return an optional `BeginAccessInst` which is not nil if such an "scope" is found.

2022-09-08 08:37:21 +02:00

20 KiB

Raw Blame History

View Raw