Threads and weak references

Using Swift
1

Hi,

I was using a weak reference in a concurrent application and and the main
thread wasn't seeing an update to a class's property made by another
thread. If I replaced the weak reference with a closure, the problem went
away.

Is there any documentation that describes this behaviour?

Thanks in advance for any help,

  -- Howard.

2

Can you provide a more concrete example of the behavior you're seeing, and the behavior you expect?

-Joe

···

On Sep 22, 2017, at 2:38 AM, Howard Lovatt via swift-users <swift-users@swift.org> wrote:

Hi,

I was using a weak reference in a concurrent application and and the main thread wasn't seeing an update to a class's property made by another thread. If I replaced the weak reference with a closure, the problem went away.

Is there any documentation that describes this behaviour?

Thanks in advance for any help,