Auxiliary fnction to the previous one for describing function calls for logging purposes.

Initializes the common parser bindle.

Dumps the contents of a `TokenSupplier` into a string.

and.

=.

What it says: this is a precedence just below NAMESPACE, for kludging purposes.

:.

,.

== or !=.

user-defined endfix.

user-defined infix or ->.

user-defined midfix or forefix.

user-defined prefix or function.

user-defined suffix, or type in type declaration.

'given'.

Assignments in `given` blocks.

after [.

> or < or <= or >=.

Logging statements.

The colon separating the parameters of an inner function from its body.

For use in headers of `for` blocks.

- as a prefix.

'foo.bar'.

not.

or.

->, >>, ?>.

* or / or %.

semantic newline or ;.

+ or -.

A vile kludge.

a kludge to let me use Go-like syntax in function definitions --- change to FMIDFIX?.

with, but ONLY when peeking ahead, otherwise it's an FMIDFIX.

When we dispatch on a function which is semantically available to us because it fulfills an interface, but we haven't compiled it yet, this keeps track of where we backtrack to.

For data that needs to be shared by all parsers.

Stores information about other parsers.

This interface allows the parser to get its supply of tokens either from the relexer directly or from a `TokenizedCodeChunk`.

Stores parse code chunks for subsequent tokenization.

This is indeed the whole of the type system as the parser sees it, because one abstract type is a subtype of another just if all the concrete types making up the former are found in the latter.