OK! Where were we?
In my last dispatch, I talked about case-lambda in guile. The gist of it is, let procedures parse their own arguments, and they can do neat stuff like multiple-arity dispatch.
Also, neat stuff like optional and keyword arguments! Consider our my-write example from last time:
(define my-write
(case-lambda
((obj port) (write obj port))
((obj) (my-write obj (current-output-port)))))
It's a little silly, to write it this way. It's not essentially one procedure with two different bodies, it's one procedure with one required argument, and one optional argument. The optional argument defaults to (current-output-port).
So, as you would imagine, there is a better way to express this "design pattern": lambda*, and its sugary friend, define*.
In this case, we would simply define my-write like so:
(define* (my-write obj #:optional (port (current-output-port))) (write obj port))
So nice, so clear. Default values are only evaluated if the argument is missing. (It's a rare Python programmer that's not surprised about Python's behavior in this regard; but I digress.)
keyword args too
Optional arguments are good at allowing for concision and extensibility, but code that uses them can be confusing to read. Actually this is a problem with positionally-bound arguments in general.
I like how Carl Worth puts it: that nice prototypes can result in inscrutable code. His solution in C is to have function names encode their arities, but we can do better in Scheme, with keyword arguments.
So let's say we want to add a "detailed" argument to my-write. We can add a keyword argument:
(define* (my-write obj
#:optional (port (current-output-port))
#:key (detailed? #f))
(if detailed?
(format port "Object ~s of type ~s" obj (class-of obj))
(write obj port)))
Invocations are really nice to read:
(my-write 'foo #:detailed? #t) =| Object foo of type #<<class> <symbol> 8c4fca8> (my-write 'foo (open-output-file "foo.log") #:detailed? #t) ; writes the same thing to foo.log
The second example gives an explicit port; and indeed, I am left wondering what it is, when I read it. Keyword arguments make for more readable code.
Keyword arguments also allow for better extensibility. But don't take it from me, take it from P. Griddy:
Most of the operators in Rtml were designed to take keyword parameters, and what a help that turned out to be. If I wanted to add another dimension to the behavior of one of the operators, I could just add a new keyword parameter, and everyone’s existing templates would continue to work. A few of the Rtml operators didn’t take keyword parameters, because I didn’t think I’d ever need to change them, and almost every one I ended up kicking myself about later. If I could go back and start over from scratch, one of the things I’d change would be that I’d make every Rtml operator take keyword parameters.
-- Paul Graham, from a talk he gave back when he didn't talk about startups so durn much
And, there's one more thing, which applies both to optional and keyword arguments: the default values are evaluated in the lexical context of their preceding arguments. So you can have a later argument referring to an earlier one. For example, Guile's compile is defined like this:
(define* (compile x #:key
(from (current-language))
(to 'value)
(env (default-environment from))
(opts '()))
;; wizardly things here
...)
See how env's default value references from? Awesome, yes? I thought so.
newness
So what's new about all this? Not much, semantically. Guile has supported lambda* and define* for more than 10 years. But now they are available in the default environment, and they are fast fast fast -- for the same reasons that case-lambda is faster now. There are special opcodes to process stack arguments into optionals, and to shuffle and bind keyword arguments, all without consing a single cell.
Also, now the toolchain knows about optional and keyword arguments, so that backtraces and printouts show them nicely. For example, my-write prints like this:
#<program my-write (obj #:optional port #:key detailed?)>
Ah, there is case-lambda*; though it is of dubious utility, given that it can only reasonably dispatch on the required and optional arity, and not on keyword args. But there it is.
In any case, I look forward to using lambda* more in the future, without speed trepidations. Just say no to rest arguments masquerading as optionals!
If you were to install the 
upstream hacking
Here goes the release log:
![[Hacker]](hacker.png){kind=small}
![[Planet]](planet.png){kind=small}
