On Mon, 14 Sep 2015 17:57:34 -0500, Sam Tobin-Hochstadt wrote: > > On Mon, Sep 14, 2015 at 6:08 PM Matthias Felleisen > <[email protected]> wrote: > > On Sep 14, 2015, at 6:06 PM, Vincent St-Amour > <[email protected]> wrote: > > > Do you mean that the style guide refers to unstable? A quick grep > didn't > > find anything. > > > > Or do you mean that the style guide should keep a discussion of > > unstable-related workflows? I would say no, since we're now > discouraging > > these workflows. > > > Yes. If you want to keep unstable, the style guide should mention > the life cycle of unstable ideas. > > [[ May I ask whether Eli was right about unstable? ]] > > > The `unstable` collection served a very useful purpose, but now that we > have a package system and a split repository, it's not longer needed in > the way that it was. Which is why it's great that Vincent has cleaned it > up.
Precisely. Many of what used to be unstable subcollects now live on as independent packages, which makes them more discoverable, and removes the specter of unstability. A lot of the rest have been merged with the relevant portions of the standard library, also making them more discoverable, and less "risky" to use. Vincent -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/m2wpvs8uf4.wl-stamourv%40eecs.northwestern.edu. For more options, visit https://groups.google.com/d/optout.
