A note for list logic jets: almost all changes include a transfer loop, where at the entry we gain a reference to a and then iterate over the list, gaining its tail and losing the list, then replacing the list with its tail. It means that at the end of the loop we still have a reference to a noun in a. We almost never lose it though, because a is 0, except for +levy/+lien, where we might break from the loop earlier.

technically the very first gain of the list is not necessary and we could unroll the loop, doing things as usual in the first iteration and starting to count the references after that, but IMO whatever gain we get from that is not worth the bloated code

bonus commit: pretty printer measured the length of the atom multiple times for some reason

u3m_soft_run now can take 0 instead of a scry gate to mean the same thing as _~, right?

It doesn't mean exactly the same thing: this will bail exit, while the prior behavior would block. But this function appears to be unused, so it's not clear that it matters.

the function is used in urwasm where the behavior is imporant.

in ++mink definition in hoon.hoon scry gate ~ always blocks. In u3m_soft_esc there is no check, so that would indeed be bail exit. That's a bug, right?

yep, this is a jet mismatch:

> .*([-:mink [[0 [%12 1+0 1+0]] ~] +>:mink] -:mink)
[1 0]
> (mink [[0 [%12 1+0 1+0]] ~])
[%2 trace=~]

Good catch. The mismatch comes from urbit/urbit#7124 and the hoon is wrong -- +mink should crash if there is no scry handler.