Let's keep this light and fun, especially for the implementor, who shouldn't be bogged down with parens-or-die commentry. How about treating it as yet another #lang, albeit one of interest as core members have an itch to scratch. Let's cross the bridge of moving docs/website/drastic stuff when there's an implementation that passes muster. Choose a silly and fun code name to start off with, a bit of self deprecation and irony goes far. The new language needs to earn the title of racket2, a name with much gravity.
I'm looking forward to #lang not(racket2) as, certainly, I'll learn new things. A whole new world drawing from the best of research and Racket. With that, bloody well have at this problem Matthew, more power to you. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CA%2BLh%3Dn2Oh_syWvM_dUGeahBHKX%3DpBJyrA1-3J1atBeeuYuGrHg%40mail.gmail.com.
