I tried a lookup table for the no_orientation_mod case in ac259e3d945056d8257c166bc572f75acf1e32b1 but reverted it in 1b8a6e510ac57e556b469f1e1d7b612b12c3e1be because I couldn't measure a speed gain. (It seemed to be under 1M moves/s, which is the normal variability range for cargo run --release --example test-cpp_port.)
I tried a lookup table for the
no_orientation_mod
case in ac259e3d945056d8257c166bc572f75acf1e32b1 but reverted it in 1b8a6e510ac57e556b469f1e1d7b612b12c3e1be because I couldn't measure a speed gain. (It seemed to be under 1M moves/s, which is the normal variability range forcargo run --release --example test-cpp_port
.)However, the default logic is now more complex:
https://github.com/cubing/twsearch/blob/a98834f47fb458dc5a2598578b75cb5bdef17c1f/examples/cpp_port/packed/packed_kstate.rs#L97-L114
It might benefit from its own lookup table, probably also stored in
PackedKPuzzleOrbitInfo
.