Thank you for the feedback!
I think this macro is a very nice idea and should indeed allow removing
most compose-i functions, except maybe for compose-3 and compose-4, which
can be examples of use of make-compose.
I added a Contributing section to the README of the Git repo:
Hi Racketeers,
Laurent Orseau asked if it’s possible for the release announcement to
include @history changes (compared to the previous release), because some
small but useful changes might go unnoticed otherwise. I think this is a
great idea, so I tried to implement the feature. The result for
> It would be nice if I don’t have to modify scribble-lib, or, failing that,
> avoid touching documenting forms. Isn’t it possible for history to know
> which defform it’s under?
A history might not appear under a defform (for better or worse).
Maybe it's easier to give a list of links to the
Hello all,
I am embarking upon a project to doing 2D graphics in Racket, so I am
starting off with various experiments, some of which include testing out
performance and replicating Processing examples.
I definitely need to do some more reading, but I am wanting to post this to
get some leads
4 matches
Mail list logo
