Confusing Constraint Re: References


#1

I’m following along, but found these two statements a bit contradictory. It may want to be clarified in future editions for readers:

and a bit forward, there is this:

:question:
It makes sense not to keep a reference to a UITouch object as that same object would need to be assigned immediately and a sentinel reference to nothing doesn’t make sense (and then there can’t be further assignment).

If the term reference is used in the figurative sense, then that would be a pointer scratching it’s butt until we assign it, value it, re-assign, repeat. We are keeping an entire table of them though.

Or is it not to add a retain cycle for it outside of the current scope and only its value?

Hope that makes sense.