Tim Cuthbertson

Another way to achieve this might be to have an `implicit` context object, which each log call accepts, and includes that context with the log statement. That way you pass...

I think those names work (though `access` still feels accurate to me too). Regarding the docs, what's the core difference? IIUC it's that using `modify` will not end up creating...

While I'm at it, it looks like koka doesn't handle arguments with spaces properly either: ``` $ koka -e print-args.kk -- 'a b c' d created : .koka/v3.1.3/clang-debug-3a5dcc/print_dash_args__main ["a","b","c","d"] ```

Oof, thanks 🤦 . I was thrown because `--include DIR` has the same effect, only `--include=DIR` works.

I'd like to improve this, so that it allows both inline and multi-argument versions `-ifoo`, `-i foo`, `--include foo` and `--include=foo`. I'm hoping that'd be a welcome contribution?

Oh, I just took a look and it seems like this is just how `System.Console.GetOpt` works. That's a shame, it's inconsistent with most of the CLIs I'm familiar with -...

I just used `foo.is-just` and it's another good argument for this rename - `foo.is-some` makes much more sense

That terminates the program unsuccessfully, but I'd still want a plain exit function which doesn't print any extra messages and does let you choose the exit code (that part's rarely...

I'm surprised `stopped` is a different branch, isn't that just another signal? FWIW in my WIP libuv process branch, I went with [an ADT for Exit-status(int) and Exit-signal(int)](https://github.com/timbertson/koka/blob/012b49c2382e59c98522b7424ad10c0ffdc062a8/lib/std/async/process.kk#L69-L83). I don't...