A future profiler seems like a performance related tool, no? (Also, I think the profiler could move into this library.)
Robby On Wed, Jul 11, 2012 at 11:01 AM, Eli Barzilay <e...@barzilay.org> wrote: > A point to consider here is that this should also be the place for a future > profiler thing, and maybe other less pref-y things... > > On Jul 11, 2012 6:39 PM, "Robby Findler" <ro...@eecs.northwestern.edu> > wrote: >> >> Better than "tools", IMO. How about "perf"? Ie, perf/future-visualizer >> and perf/optimization-coach/ ? >> >> Robby >> >> On Wed, Jul 11, 2012 at 10:10 AM, Vincent St-Amour <stamo...@ccs.neu.edu> >> wrote: >> > (Performance) tuning? >> > >> > Vincent >> > >> > >> > At Wed, 11 Jul 2012 10:04:46 -0500, >> > Robby Findler wrote: >> >> >> >> tools seems like too generic of a word. Is there something like >> >> "performance-debugging" that isn't so long? >> >> >> >> Robby >> >> >> >> On Wed, Jul 11, 2012 at 9:58 AM, Vincent St-Amour >> >> <stamo...@ccs.neu.edu> wrote: >> >> > At Wed, 11 Jul 2012 01:33:02 -0400, >> >> > Eli Barzilay wrote: >> >> >> Or maybe add a new "tools" collection for other similar things? >> >> > >> >> > I'm about to push the new version of Optimization Coach (formerly >> >> > Performance Report). Since it now works with any language (not just >> >> > TR), >> >> > it would make sense to move it outside of the `typed-racket' collect. >> >> > It would be a good candidate for the `tools' collection. >> >> > >> >> > Vincent > > > _________________________ > Racket Developers list: > http://lists.racket-lang.org/dev > _________________________ Racket Developers list: http://lists.racket-lang.org/dev
