> Yes - see
> https://www.gnu.org/software/kawa/Application-and-Arguments-Lists.html
>
> The basic idea is you can create "arglist" or an "argvector" which is a
> kind of list
> or vector, except the keywords are "marked".  You can then pass this
> arglist
> or argvector to apply.
>
> You can also use "slice" syntax, which is more flexible:
>
>     (fun @arglist) === (apply fun arglist)
>
> You can combine arglists:
>
>     (define xargs (arglist 1 2 key: 3))
>     (apply fun (arglist 9 8 @xargs))

> Regular apply suffixes.

Thanks. Using a special arglist object seems much nicer than the
keyword-apply approach.

Here's some actual code I wrote making use of keyword-apply:

;; Usage: (cache-http cache-name url [keyword-args])
;; Any keyword-args are passed to http-sendrecv/url.
(define cache-http
   (make-keyword-procedure
    (lambda (kw-syms kw-args cache-name url)
      (let (...)
        ...
        (let-values
            (((status headers input)
              (keyword-apply http-sendrecv/url kw-syms kw-args (list url))))
          ...)))))

There are several problems with this:

- Had to use `make-keyword-procedure` instead of ordinary `define` or
`lambda`.

- Had to write a comment explaining the "real" argument list accepted by
the procedure.

- Had to use keyword-apply instead of apply (177 also has this problem).

- kw-syms and kw-args are separate lists - would arguably be neater if
it was a single collection.

allow-other-keys/splicing would express this much more nicely.

Does Kawa have allow-other-keys in the lambda-list in some form? I
perused <https://www.gnu.org/software/kawa/Extended-formals.html> but
didn't catch syntax for it.
<https://www.gnu.org/software/kawa/Application-and-Arguments-Lists.html>
is about the other side (caller) as far as I can tell.