Orkuncakilkaya
7834b26ef8
Every pool thread runs the worker at once with the same states, so a mut state in a worker was a race nothing reported. check_worker_ref refuses a worker whose leading states include a mut one; threads.ludic's total moves into the words the worker is handed, under the mutex. The seeds are regenerated (ludic-dev reseed). ludic-dev test 305 passed, selfhost-test 33 passed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
701 B
701 B
bump: minor
type: feature
A Job.parallel_for worker may read a state but not change one. Every pool thread runs the
worker at once, and the runtime hands each call the same state, so a worker that took a state as
mut raced on it with nothing to say so. The compiler now refuses it (fn bump: a worker runs on every core at once, so it may read CountState but not change it): a result goes into ctx, a
shared count through a Sync handle kept in the state. A function's signature already says what it
touches, so this is the whole check - the same one a parallel scheduler needs to run two systems at
once. examples/library/threads.ludic keeps its total in the words it hands the worker.