For example, for unit tests we have index-independent topology comparison function: #112794.
Also, for mesh topogy utils we have BLI_mesh.hh and BLI_mesh_mapping.hh\
Please, avoid dependency cycle in your project. The fact of the behavior change is not a bug and expected UB in case of existing dependency cycle.
I strongly do not think mesh have to have any such algorithmic methods at all, this is not zero-cost and purely the purpose-depend abstraction.
Ops, did not read report body, thought you means modifier parenting
Still valid case just constraints is few different topic\
In this case, probably you should create another one object with…
Thanks for report, geometry nodes are proposed to totally replace all other modifiers and they does not work with any other modifiers. You can expect something, but this is not really expected.…
This is just how blender work.
I do not think you could do anything on a python to change geometry nodes behavior.
Trust me, when you do something in geometry nodes, int/int8_t/float does not really make a difference.
