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
Like #19 but now we allow repeated generators in the object. The users should be able to specify if they want the same generators to be swapped, and how. If they do not specify anything, then fastcompose should compose f and g without swapping the same object. This is analogous to "swapfree" symmetries in https://arxiv.org/abs/1904.12974 .
I know this specifications suck a bit, but they are a starting point to make clear what is that we want to achieve conceptually :)
The text was updated successfully, but these errors were encountered:
Like #19 but now we allow repeated generators in the object. The users should be able to specify if they want the same generators to be swapped, and how. If they do not specify anything, then fastcompose should compose
f
andg
without swapping the same object. This is analogous to "swapfree" symmetries in https://arxiv.org/abs/1904.12974 .I know this specifications suck a bit, but they are a starting point to make clear what is that we want to achieve conceptually :)
The text was updated successfully, but these errors were encountered: