libera/#clasp - IRC Chatlog
Search
2:28:05
drmeister
Bike: If I have a vector with N elements and N threads where each thread updates its own element of the vector - is that going to work?
2:30:54
Bike
i think that practically speaking it will probably work, but ideally we should clue C++ in here
2:32:27
drmeister
I can do something more complicated where each thread puts updates into a queue but it seems straightforward to just update a counter in a vector.
2:50:25
drmeister
Line 19 I use pmapcar to analyze several files and they call 'progress-callback' that updates a counter depending on the file-index.
2:51:36
Bike
i think that should be fine. i mean, i would expect it to work now, and if it doesn't, i think it's just a matter of convincing C++, and we already did that for instance racks so i don't think it will be too involved hopefully
2:52:53
drmeister
I've been reading the lparallels manual. I think delay will work this way. I'm not sure if it captures other lexical variables - but it seems to be able to.
2:53:07
Bike
"Like futures and speculations, a delay is also a promise associated with some code. However instead of being fulfilled in parallel, a delay is fulfilled when force is called upon it."
2:53:29
Bike
and anyway you don't really care about the value if it's just a progress bar, so maybe you can just start a thread?
3:00:21
Bike
is there a reason you want to use lparallel rather than just a primitive thread starting function?