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
As we saw in #75, due to the nested structure of the Collection that keeps references to itself via the AnkiDataFrames that it posesses in __items and __original_items, it does not get garbage collected when it goes out of scope. Only when __items and __original_items are manually deleted, the GC gets triggered.
This is likely not a practical issue, but it's not nice either.
The text was updated successfully, but these errors were encountered:
Perhaps it would even be better to completely avoid an AnkiDataFrame having to implicitly access the Collection, because this doesn't really make sense from a structure point of view. Rather, the Collection could be explicitly used in the interface
As we saw in #75, due to the nested structure of the
Collection
that keeps references to itself via theAnkiDataFrames
that it posesses in__items
and__original_items
, it does not get garbage collected when it goes out of scope. Only when__items
and__original_items
are manually deleted, the GC gets triggered.This is likely not a practical issue, but it's not nice either.
The text was updated successfully, but these errors were encountered: