Open gabrielle-ohlson opened 3 years ago
I think I agree here -- in cases where the carrier stopping distance is short enough, juggling/kickbacks should be avoided.
If I recall, the current backend code does have a notion of carrier stopping distances and so probably could do exactly as suggested (at least with suitably-spaced stitches).
I suspect it will never work for a knit and a tuck on adjacent needles (no place to put the carrier), but it would be interesting to run some kcode tests to see if there is some distance for which it does work.
Although the kniterate cannot perform knits and tucks in one kcode pass, it would be nice to have the separated passes flow together better. Currently a knitout pass like so:
Results in something like this when converted to kcode:
When it would ideally look more like this:
The kniterate often encounters an issue when juggling a carrier in the middle of knitting—the working yarn will get a bit caught on the pegs and then won't be at the correct angle to successfully knit, resulting in dropped loops when resuming knitting.
Here's what that might look like in knitout: