Re: [racket-users] surprising [to me and students] printer behavior with #:transparent

Ah, got it, makes perfect sense through that lens -- thanks! On Tue, May 16, 2017 at 9:37 AM, Philip McGrath wrote: > The printer tries to produce an expression that you could copy, paste, and > evaluate. Transparent structs aren't quotable but do support >

Re: [racket-users] surprising [to me and students] printer behavior with #:transparent

The printer tries to produce an expression that you could copy, paste, and evaluate. Transparent structs aren't quotable but do support constructor-style printing, so the printer uses constructor-style printing for values that contain transparent structs. (Apparently you can configure this in

[racket-users] surprising [to me and students] printer behavior with #:transparent

Hi all, In my course here on campus, I have students use #lang racket and we put #:transparent on our struct definitions for easier REPL interactions. A student was confused by the different printer-behavior between a and b in the attached screenshot, and I can't think of a reason for the