Reference cycle with unowned / weak inside autoclosure

Unless it's a global, it appears to be an array-valued member of self, no? And since it is passed as an escaping autoclosure argument, its evaluation is delayed all the way until acceptableContentTypes() in the first method. So there's the implicit capture of self, strongly.

Am I making sense? :smiley: