Why is it important to specify the order of check runs?

I found this in the README but have no idea what it’s trying to tell me:

      -o ORDER, --order ORDER
                            Comma separated list of order arguments.
                            The execution order is determined by the order of the check
                            definitions and by the order of the iterable arguments.
                            A section defines its own order. `--order` can be used to
                            override the order of *all* sections.
                            Despite the ITERATED_ARGS there are two special
                            values available:
                            "*iterargs" -- all remainig ITERATED_ARGS
                            "*check"     -- order by check
                            ITERATED_ARGS: font
                            A sections default is equivalent to: "*iterargs, *check".
                            A common use case is `-o "*check"` when checking the whole
                            collection against a selection of checks picked with `--checkid`.

[anthrotype]

Sure sure! I like to play the python police when I’m bored 😃 🐍 👮‍♂️

[madig]

Ok, that I understand, thanks. This needs to be in the docs 😃 Is there any particular reason the argument reads “*checks”, etc.? I’d find something like --order [each_check_all_fonts|each_font_all_checks] easier to understand.