When you have a huge enumeration, like we do here, I think importance is extremely difficult to evaluate for a reasonably large audience but topics are easy to group. If you don't mind, let's leave it alone.
On Aug 2, 2012, at 11:46 AM, Sam Tobin-Hochstadt wrote: > On Thu, Aug 2, 2012 at 11:44 AM, Matthias Felleisen > <matth...@ccs.neu.edu> wrote: >> >> 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. > > I attempted to order them by (my impression of) importance to Racket > programmers. For example, the new error messages are likely to be the > first thing people notice about v5.3. > >> >> >> 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 >> > > > > -- > sam th > sa...@ccs.neu.edu
smime.p7s
Description: S/MIME cryptographic signature
_________________________ Racket Developers list: http://lists.racket-lang.org/dev
