FWIW, there is an aspect to private protocol requirements that's separate from sealed protocols, and one I've wished for myself before on multiple occasions: the ability to implement generic functionality in an extension to the protocol itself, in terms of its own (private) requirements; e.g., default implementations for common properties/methods in terms of private requirements. From a similar previous thread: