Currently, a Surface provides an OrbitClosure object through orbit_closure(). However, this object is not updated correctly, e.g., when the OrbitClosure goal consumes its cache.
The sharing is probably introduced because FlowDecompositions also needed the orbit closure object at some point. Since this is fixed in sage-flatsurf, we could move it to the OrbitClosure goal and consume caches correctly there.
Currently, a Surface provides an OrbitClosure object through
orbit_closure(). However, this object is not updated correctly, e.g., when theOrbitClosuregoal consumes its cache.The sharing is probably introduced because
FlowDecompositionsalso needed the orbit closure object at some point. Since this is fixed in sage-flatsurf, we could move it to theOrbitClosuregoal and consume caches correctly there.