In reply to @ithinuel:matrix.org
I'd say it mostly depends on how much you value the PIO instruction slots.
There's only 32 of them, so 1 instruction is already more than 3% of the available space.
But overall for your firmware, if it makes it use an extra 10k (I'm exagerating on purpose) of Flash or if your firmware runs twice as slow, it may be worth using an extra slot of PIO 🤷

fn move_map(mov: Movement) -> IntoIter<u32, 2> {
    [mov.0, mov.1].into_iter()
}

fn move_map(mov: Movement) -> IntoIter<u32, 2> {
    match mov {
        Movement(0, delay) => [0, delay.saturating_add(8)],
        Movement(steps, delay) => [steps, delay],
    }
    .into_iter()
}

In reply to @jannic:matrix.org
It also depends on what else you expect to do with the pio. If you don't plan to install any other pio program in parallel, saving an instruction doesn't help at all.

let op = InstructionOperands::JMP { condition: JmpCondition::Always, address: prog.addr };
sm.exec_instruction(Instruction::decode(op.encode(), prog.side_set).unwrap());

where prog is

pub struct TmcProgram<P: PIOExt> {
    prog: InstalledProgram<P>,
    addr: u8,
    side_set: SideSet,
}

In reply to @9names:matrix.org
https://github.com/jannic/rp2040-flash/blob/master/examples/flash_example.rs