[racket] values primitive blocks future execution

Never mind, it was from running it in DrRacket. From the command line, 
it doesn't block, so it parallelizes a bit, but it syncs a lot on 
allocations. The code:

   http://pastebin.com/dEE1JfXF

It uses two futures because that's how my randomized search for 
something that worked turned out. I'm not sure whether that's better or 
worse than one future.

Neil ⊥

On 02/21/2013 04:10 PM, Neil Toronto wrote:
> After converting everything to Typed Racket and using no `for' macros,
> I'm also getting a block on "prim_indirect" in the dummy renderer. It
> would be nice to know which primitive it's referring to, especially
> since I can't find anything but unsafe operations in the expanded code.
>
> Neil ⊥
>
> On 02/21/2013 03:53 PM, Dmitry Cherkassov wrote:
>> Just an update.
>>
>> I've improved[1] a code a bit and it seems that values primitive has
>> went away: http://ompldr.org/vaGpweQ
>> but now it's [prim-indirect] stuff that blocks everything.
>>
>> [1] code: http://pastebin.com/csst2NCy
>>
>> --
>> With best regards,
>> Dmitry
>>
>>
>> ____________________
>>    Racket Users list:
>>    http://lists.racket-lang.org/users
>>
>