Context Navigation

Changes between Version 2 and Version 3 of Ticket #30307, comment 28

v2	v3
8	8	Still, I don't know how we should separate the symmetry code properly. My idea so far was to let the parent do the symmetrizing work and return the parent with the corresponding symmetries, and construct an element from it, then assign the components. But this doesn't work so well when the element itself such as in `antisymmetrize` is taken into account.
9	9
10		Alternatively, it would be nice do define maps (morphisms) between parents doing that work and cache those morphisms. But that is something I don't know how to do in a nice and proper way. For example, if ~~the one antisymmetrizes in the variable~~ where the components are already symmetric, it's simply the "zero morphism".
	10	Alternatively, it would be nice do define maps (morphisms) between parents doing that work and cache those morphisms. But that is something I don't know how to do in a nice and proper way. For example, if one antisymmetrizes in the variables where the components are already symmetric, it's simply the "zero morphism".