Thanks for looking into that bug Alex, glad to know it’s already being handled by a future swift version.
I was wondering if I could ask one more question. The design I was trying to accomplish was for a protocol to expose a publicly gettable, privately settable property (which is why I used the fileprivate inherited protocol), and then have an extension expose public functions to modify the property. I gathered from a variety of old stack exchange posts that this kind of setup used to work to some degree, which is why i was trying to implement it.
Looking though some old forum threads, I’m definitely not alone in wishing for this:
Do you know of any better workarounds for this pattern? Is there any chance of this being formally introduced to Swift?
Thanks again,
-Ruka