mikeash
Found my first Swift bug by inspecting code, not encountering a crash or bad behavior. Hooray open source! https://bugs.swift.org/browse/SR-192
Joe Groff
@mikeash Good catch. We do plan to make weak references use a side table implementation like ObjC so we can eagerly reclaim their memory.
-
-
@jckarter I like how it is now! (Bug aside.) But of course I defer to your wisdom. - View other replies
-
@mikeash It's nice for perf, yeah, but leaking the memory is unacceptable for things like outlets and delegates that get hit infrequently. -
@jckarter Given the small quantity involved it seems OK to have it stick around for a while. -
@mikeash Hard to justify anything sticking around longer than it needs to on iOS/watchOS. - View other replies
-
@mikeash Maybe there's a clever solution where it lazily reclaims except in low memory situations…seems like you need the same bookkeeping. -
@jckarter You could do something like a trial load of all weak refs in the app, without tracking them on a per-object basis.
-
-
@mikeash (That's why the reference counting functions were renamed to "unowned" recently.)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.