Thanks Matthew!
On Feb 23, 2014 5:01 PM, mfl...@racket-lang.org wrote:
mflatt has updated `master' from e0a1a40fd4 to 22617b7800.
http://git.racket-lang.org/plt/e0a1a40fd4..22617b7800
=[ One Commit ]=
Directory summary:
42.2%
Is anyone else seeing strange behavior in DrRacket since this latest round
of DrRacket-related commits? Here's what I'm seeing:
-With definitions/interactions side by side, sometimes the vertical scroll
bar in the interactions window disappears for no reason.
-Saving a file can sometimes render
is
definitely helping me hone in on another one (the one you saw while
looking
at an error in drracket).
(The commit below actually fixes one bug.)
Robby
On Monday, November 26, 2012, James Swaine wrote:
Is anyone else seeing strange behavior in DrRacket since this latest
round
james:
- added would-be-future (a5676e9a)
Would-be-future is a special type of future that always executes
sequentially and records all potential barricades a regular future would
encounter.
- added futures visualizer (b6f71ec4)
The futures visualizer is a graphical profiling tool
I noticed the large amount of allocation going on when I was using
mandelbrot to test my fixes to the visualizer last week -- I'll take a
look. I wrote an allocation hotspot profiler tool that may end up as part
of the visualizer in some form, so I can try running it on your code.
On Tue, Jul
I don't know if there's consensus here yet, but it seems like the best
thing is to move racket/future/visualizer into a top-level:
future-visualizer. Then racket/future/trace will become
future-visualizer/trace. If that sounds reasonable, I'll go ahead and move
them.
On Thu, Jul 12, 2012 at
/
43.6% collects/scribblings/guide/
6.5% collects/scribblings/**reference/
11.1% collects/tests/future/
~~
b6f71ec James Swaine jamesswa...@racket-lang.org 2012-02-29 11:43
:
| Add futures visualizer, improvements to futures logging
:
A collects/racket/future/**private
On Tue, Jul 10, 2012 at 10:51 PM, Robby Findler ro...@eecs.northwestern.edu
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 ...
+1
On Thu, Mar 22, 2012 at 3:15 PM, Matthias Felleisen
matth...@ccs.neu.edu wrote:
very useful
On Mar 22, 2012, at 3:26 PM, Stephen Chang wrote:
Would anyone find it useful to have a triangle primitive in
slideshow/pict? How easy would it be to add one?
_
Racket
Here's the release note for futures:
- futures: added fsemaphores; 'future' primitive now no longer freezes
futures;
improved the logging messages futures produce
-James
On Fri, Apr 29, 2011 at 12:05 PM, dev-requ...@racket-lang.org wrote:
Send dev mailing list submissions to
I'm getting a module mismatch error after pulling from git that I can't seem
to make go away despite my best efforts. Here's the message:
Starting program: /Users/jamesswaine/plt-cur-build/racket/racket3m
~/plt/collects/tests/future/future.rkt
link: module mismatch, probably from old bytecode
and seeing if you still see the error (without rebuilding them).
Something like this:
find ~/plt -type f -name \*.zo -exec rm {} \;
Robby
On Mon, Feb 14, 2011 at 1:44 PM, James Swaine james.swa...@gmail.com
wrote:
plt-cur-build isn't a source tree, it's just my build directory.
On Mon, Feb
you get from the script after you deleted the zos and
before you rebuilt them?
On Mon, Feb 14, 2011 at 2:58 PM, James Swaine james.swa...@gmail.com
wrote:
This didn't seem to fix it. After running this I tried again to make all
the collects from scratch, but I still get the same error
Do you know, by chance, if your processor supports the SSE2 extensions? It
looks like you're compiling on a 32-bit Mac...
(In the meantime, if you don't need to use parallel futures, you can work
around this by disabling futures in the build. Rerun the configure script
and pass
14 matches
Mail list logo
