<p>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...</p>
<div class="gmail_quote">On Jul 11, 2012 6:39 PM, "Robby Findler" <<a href="mailto:robby@eecs.northwestern.edu">robby@eecs.northwestern.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Better than "tools", IMO. How about "perf"? Ie, perf/future-visualizer<br>
and perf/optimization-coach/ ?<br>
<br>
Robby<br>
<br>
On Wed, Jul 11, 2012 at 10:10 AM, Vincent St-Amour <<a href="mailto:stamourv@ccs.neu.edu">stamourv@ccs.neu.edu</a>> wrote:<br>
> (Performance) tuning?<br>
><br>
> Vincent<br>
><br>
><br>
> At Wed, 11 Jul 2012 10:04:46 -0500,<br>
> Robby Findler wrote:<br>
>><br>
>> tools seems like too generic of a word. Is there something like<br>
>> "performance-debugging" that isn't so long?<br>
>><br>
>> Robby<br>
>><br>
>> On Wed, Jul 11, 2012 at 9:58 AM, Vincent St-Amour <<a href="mailto:stamourv@ccs.neu.edu">stamourv@ccs.neu.edu</a>> wrote:<br>
>> > At Wed, 11 Jul 2012 01:33:02 -0400,<br>
>> > Eli Barzilay wrote:<br>
>> >> Or maybe add a new "tools" collection for other similar things?<br>
>> ><br>
>> > I'm about to push the new version of Optimization Coach (formerly<br>
>> > Performance Report). Since it now works with any language (not just TR),<br>
>> > it would make sense to move it outside of the `typed-racket' collect.<br>
>> > It would be a good candidate for the `tools' collection.<br>
>> ><br>
>> > Vincent<br>
</blockquote></div>