An hour and a half ago, Robby Findler wrote:
> On Tue, Jul 10, 2012 at 10:41 PM, Eli Barzilay <e...@barzilay.org> wrote:
> >
> > 10 minutes ago, Robby Findler wrote:
> >> It is the future visualizer so I thought it belonged with the
> >> visualizer. No?
> >
> > (You mean "... belonged with the futures", right?)
>
> Right. :)
>
> >> Alternative suggestions welcome.
> >
> > I think that it fits well with other meta-analysis kind of tools like
> > errortrace and the profiler, so a new toplevel collection seems to
> > make perfect sense. I don't have a concrete suggestion better than
> > "future-visualizer" though since I don't know what it does exactly.
> > Maybe "future-debugger" or "future-tracker" or something like that?
>
> I think we have too many top-level collections and making a new one,
> especially with "future-" in the name seems like a step in the wrong
> direction.
If more tools will be there, then it could be "futute/something"...
Or maybe add a new "tools" collection for other similar things?
But in any case, having a new toplevel collection seems much less of a
problem than having a tool in racket/*.
> ("visualizer" is a better word than "debugger" or "tracker" for what
> it does, IMO, altho it has elements of those. But if you read the docs
> in the Guide about it, you should get some idea what it does.)
An hour and a half ago, James Swaine wrote:
>
> Agreed, "debugger" and "tracker" don't really adequately describe
> it. Maybe "future-profiler" is another option, but maybe confusing
> since we already have "profiler". (But I still think "visualizer"
> is best, IMHO).
(I did say that I don't know what it's doing so I was blindly
guessing...)
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_________________________
Racket Developers list:
http://lists.racket-lang.org/dev
