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
Flatpack (and in particular the methods flatpack.flatten and .unflatten) correctly handle cyclic data and shared substructure involving pointers, but from reading the source for reflect.DeepEqual it's clear that it's possible to encounter cycles that do not involve pointers.
In particular, slices and maps are both reference types which can share substructure and result in circular references (in conjunction with interface types, which, while they may internally be implemented with a pointer, cannot by themselves result in shared substructure or cycles).
Flatpack
(and in particular the methodsflatpack.flatten
and.unflatten
) correctly handle cyclic data and shared substructure involving pointers, but from reading the source forreflect.DeepEqual
it's clear that it's possible to encounter cycles that do not involve pointers.In particular, slices and maps are both reference types which can share substructure and result in circular references (in conjunction with interface types, which, while they may internally be implemented with a pointer, cannot by themselves result in shared substructure or cycles).
(Moved from CodeCity)
The text was updated successfully, but these errors were encountered: