Check permutation overlap/collision

[tdib]

When queueing multiple moves such as R and L, they are put into a queue, and hence do not happen simultaneously. These moves can happen at the same time as the cubies are entirely unique across both movies, and will not affect one another.

This is primarily an issue with implementations of advanced moves like M, E, and S, which are each implemented using two moves and a rotation.

Screen.Recording.2023-08-16.at.4.53.16.pm.mov

[tdib]

While not exactly addressing this issue, slice/advanced moves are now implemented differently, so this issue is less relevant. In the case of performing L and R moves at the same time, this is still an issue.

I looked into a solution that chunked non-conflicting moves together, and executing those moves all at once, but they did not happen synchronously and caused some strange artefacts.

Screen.Recording.2023-11-11.at.11.37.33.pm.mov

[tdib]

With the implementation of wide moves, this becomes more of an issue :(

Wide moves could be implemented using a different encoding like slice moves were but it would be better to fix this issue directly.

Screen.Recording.2023-11-12.at.11.58.03.am.mov