B::Concise sequence numbers and null ops

B::Concise does not give sequence numbers to null ops even if they are
part of the execution order.  Ideally, there should be no null ops in
the execution order to begin with, but, if it does happen, B::Concise
is not helpful in debugging it.  In fact, its output is quite
confusing:

1        <;> nextstate(main 1 -e:1) v ->-

How can an op in the execution chain be pointing to something not in
the execution chain (the ->- at the end)?

It has been working this way since c27ea44e678f.  Would it be okay to
change this?

• B::Concise sequence numbers and null ops by Father Chrysostomos
• Re: B::Concise sequence numbers and null ops by Paul Johnson
• Re: B::Concise sequence numbers and null ops by Father Chrysostomos