In racket/pretty, pretty-print is like print and pretty-write is like write. In scheme/pretty, pretty-print is like write.
So probably the better change is to stick with racket/pretty and use pretty-write instead of pretty-print. Robby On Wed, Jul 13, 2011 at 9:57 PM, Guillaume Marceau <gmarc...@gmail.com> wrote: > On Thu, Jul 7, 2011 at 12:44 PM, Matthew Flatt <mfl...@cs.utah.edu> wrote: >> * All contracts for primitives print as lists. > > > I traced this down to the change from (require scheme/pretty) to > (require racket/pretty). > > I don't understand how that's causing the bug, but reverting to > (require scheme/pretty) fixes things. > > Ryan, can you pull this fix into the release branch? It's commit > 452f3a14fb7b25e6c54d08abdb8770fb20e68752 > > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/dev > _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
