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?)
> 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?
> On Tue, Jul 10, 2012 at 9:34 PM, Eli Barzilay <e...@barzilay.org> wrote:
> > This commit adds a bad dependency from the core to framework.
> > Fixing it is probably not hard, but it leads to an obvious
> > question:
> >
> > Why is this in racket instead of some new collection?
--
((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
