This is really ugly, but I don't see any way to improve it either. Maybeif the type of &classInstance.method was actually a special "pointer-to-class-method" type that implicitly down-casted to adelegate, it would be possible to safely use &o.watch instead...I agree. Is the only reason to have a weak connection?
Yes. Weak connections are the only reason.
