Matthew, > If your goal is readable code, why not add some sugar?
That's a perfectly good solution. > More broadly, it feels like there's plenty of room for new > macro-definition and syntax-processing forms that suit different > ergonomic needs: readability, automatic error messages, debugging, and > so on. That's pretty much what I had in mind. > Interesting question why more of them don't exist. For `#lang > br` I made a set that were designed for simplicity and > readability. [1] These looks interesting, thanks! I'll have a closer look later. I guess that some people would object to making all-upper-case a semantic marker, but in terms of readability this looks nice. Konrad. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
