Re: [racket-users] Constructor-style printing for sets?

> On Jun 10, 2016, at 12:54 PM, Robby Findler > wrote: > > On Fri, Jun 10, 2016 at 11:51 AM, Alex Knauth wrote: >> >> I was thinking of that too, but the problem is that the constructor-style >> printing deals with s-expressions, while the

Re: [racket-users] Constructor-style printing for sets?

On Fri, Jun 10, 2016 at 11:51 AM, Alex Knauth wrote: > >> On Jun 10, 2016, at 11:18 AM, Robby Findler >> wrote: >> >> I view the mechanism that DrRacket's constructor-style printing uses >> is a kind of add-on layer to avoid incompatibility

Re: [racket-users] Constructor-style printing for sets?

> On Jun 10, 2016, at 11:18 AM, Robby Findler > wrote: > > I view the mechanism that DrRacket's constructor-style printing uses > is a kind of add-on layer to avoid incompatibility with standard > Scheme-style printing that we were using back in the day. So, it is

Re: [racket-users] Constructor-style printing for sets?

I view the mechanism that DrRacket's constructor-style printing uses is a kind of add-on layer to avoid incompatibility with standard Scheme-style printing that we were using back in the day. So, it is useful for a small set of classes of values and that for modern things in Racket (like sets,

Re: [racket-users] Constructor-style printing for sets?

> On Jun 6, 2016, at 10:24 PM, Alex Knauth wrote: > > 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

[racket-users] Constructor-style printing for sets?

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