In some cases, the Set.globalConnectedSets list for set X contains X in it, implying that a set is its own neighbor.
Only issue identified that this causes is related to trimming, when trim status of set neighbors is checked, skewing results for a set based on the check of its own trim status.
Unsure of the origin of this issue, but it occurs prior to any combination of the neighbor lists, i.e. prior to initiating the trim search. This being said, when neighbor lists are joined (see Issue #17) to perform the global trim, there are more instances of a set having itself erroneously listed as a neighbor.
Current working resolution (in Pull Request #19 already) requires iterating through set list, removing all instances of a sets own id being listed in the neighbor list.
In some cases, the Set.globalConnectedSets list for set X contains X in it, implying that a set is its own neighbor. Only issue identified that this causes is related to trimming, when trim status of set neighbors is checked, skewing results for a set based on the check of its own trim status.
Unsure of the origin of this issue, but it occurs prior to any combination of the neighbor lists, i.e. prior to initiating the trim search. This being said, when neighbor lists are joined (see Issue #17) to perform the global trim, there are more instances of a set having itself erroneously listed as a neighbor.
Current working resolution (in Pull Request #19 already) requires iterating through set list, removing all instances of a sets own id being listed in the neighbor list.