[racket] future

From: Noel Welsh (noelwelsh at gmail.com)
Date: Mon Aug 29 16:30:17 EDT 2011

On Mon, Aug 29, 2011 at 8:05 PM, Eli Barzilay <eli at barzilay.org> wrote:
> There's also the semi-popular syntax extension change, like {E ...}
> expanding to (λ () E ...), but that looks very confusing with
> something like (thread {(printf "foo\n")}) -- so maybe do that with
> the outer form: {thread (printf "foo\n")}.  Or maybe do that with a
> macro instead: (e thread (printf "foo\n")), which will probably go the
> way of `nested'.

Yeah, what about solving the problem of lambda's verbosity directly?
If fn or \ was shorthand for lambda, or

{ a1 ... | expr ... }

expanded to

(lambda (a1 ...) expr ...)

it wouldn't be necessary to create all these duplicate forms to avoid
writing (lambda () ...) This would cut down on code, and also make the
language more consistent.


Posted on the users mailing list.