You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The LayoutItem tuple contains a strong reference to the targetItem view. This can cause a memory retain cycle if the view itself maintains a strong reference to the layout item tuple.
Maybe a possible fix would be to make LayoutItem a final class with a weak reference to targetItem.
Of course the necessity of LayoutItem is questionable in the first place, because the layout constraint already has a unowned (!) reference to the two parties participating in the constraint (firstItem, secondItem).
The text was updated successfully, but these errors were encountered:
The
LayoutItem
tuple contains a strong reference to thetargetItem
view. This can cause a memory retain cycle if the view itself maintains a strong reference to the layout item tuple.Manuscript/Sources/LayoutItem.swift
Line 34 in bb21c1c
Maybe a possible fix would be to make
LayoutItem
afinal class
with a weak reference totargetItem
.Of course the necessity of
LayoutItem
is questionable in the first place, because the layout constraint already has aunowned
(!) reference to the two parties participating in the constraint (firstItem
,secondItem
).The text was updated successfully, but these errors were encountered: