The reader for `curly-infix` can use a read-table to alter how
`{<infix-expression>}` is read. The result can the be passed
to the language after the `#lang curly-infix` which in the
example is just `racket`, but could be something else.
Hmmm. Maybe I should make a `curly-infix` wrapping `infix` from my `infix` package.
My guess is Racket/PLT scheme's history as a language for teaching programming to students.
Racket has some other things that are non-lispy. Support for alternate (maybe non-SEXP) syntax readers and for loops come to mind.
At least it's all simple. Sometimes terrifyingly simple, but simple.
They're useful too. Non-SEXP reader could be used to create a non-infix dialect of Racket. Loop macros like for/or can be used as a more ergonomic way than recursive functions to walk a list to find/transform one of its elements.