If I run this program: #lang racket (set 1 2 3)
It prints out the value: (set 1 2 3) That's wonderful! It uses nice constructor-style printing, just like I wanted. That was without changing the printing settings from the default print mode. However, if I change DrRacket's printing settings to use constructor-style printing instead, I get this: (immutable-custom-set ...) The constructor-style printing mode in DrRacket uses `print-convert` from `mzlib/pconvert` to do this, and the `racket/set` library already uses `gen:custom-write` for constructor-style printing. Should `racket/set` sets also use a property similar to `prop:print-converter` that `print-convert` can recognize and use? Or should sets be another case in the implementation of `print-convert`? Alex Knauth -- 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.
