Why? They are currently grouped according to features, e.g., class contracts and class abstract, and placed into adjacent groups, e.g., classes next to generics.
On Aug 2, 2012, at 11:24 AM, Sam Tobin-Hochstadt wrote: > I think the below should be somewhat reordered, as follows: > > On Thu, Aug 2, 2012 at 11:16 AM, Ryan Culpepper <r...@cs.utah.edu> wrote: >> * Most error messages use a new multi-line format >> * The new `racket/generic' library >> * The contract library comes with support for >> * The futures visualizer >> * Optimization Coach >> * Typed Racket supports function definitions with keyword arguments >> * A new `json' library >> * The `class' form supports declaring a method abstract. >> * The new `images/flomap' library >> * `racket/string' is extended > -- > sam th > sa...@ccs.neu.edu > _________________________ > Racket Developers list: > http://lists.racket-lang.org/dev
smime.p7s
Description: S/MIME cryptographic signature
_________________________ Racket Developers list: http://lists.racket-lang.org/dev