Simple fixed size cache mainly intended for use in ZincWorkerImpl with the following properties - Elements are lazily initialized upon first access - Cached element ordering is preserved. The earliest available cache entry which is probably a compiler instance will always be returned first, and it will always be put back in the cache in the same position. This is important because each compiler instance is JITed independently. So with a stable ordering so we can bias towards reusing an already warm compiler.

A combination lock & cache; users provide a key, value-factory, and a body function to be called with the value. KeyedLockedCache ensures that the body function is called with the computed/cached value sequentially.

The standard logging interface of the Mill build tool.

Contains these primary logging methods, in order of increasing importance:

- debug : internal debug messages normally not shown to the user; mostly useful when debugging issues

- ticker: short-lived logging output where consecutive lines over-write each other; useful for information which is transient and disposable

- info: miscellaneous logging output which isn't part of the main output a user is looking for, but useful to provide context on what Mill is doing

- error: logging output which represents problems the user should care about

Also contains the two forwarded stdout and stderr streams, for code executed by Mill to use directly. Typically these correspond to the stdout and stderr, but when show is used both are forwarded to stderr and stdout is only used to display the final show output for easy piping.

A wrapper around os.Path that calculates it's hashcode based on the contents of the filesystem underneath it. Used to ensure filesystem changes can bust caches which are keyed off hashcodes.

The result of a task execution.