Yeah it could be risky. Might be a feature best used inside the library implementation but not exposed in the public interfaces. I’m not sure how this would in

Yeah it could be risky. Might be a feature best used inside the library implementation but not exposed in the public interfaces. I’m not sure how this would interact with the API compatibility Swift has. Maybe that would help authors.