That is the reason. Thanks for posting a clear explanation.

I am afraid this is not the reason. A protocol requirement does not define if a conforming type implements conformance as a computed property or not. {get, set} if the protocol is not a requirement for a computed priory even though it rather looks like it might be.