3 ms·
Interestingly enough, my threads here are deterministic because they always just wait for the execution to finish. So they're the same as not having them. My
by Verdex 3y ago
Interestingly enough, my threads here are deterministic because they always just wait for the execution to finish. So they're the same as not having them.
My plan was to go back and store off the threads generated and have something else wait for them, but I needed to think it through so that it could be done in a way to get deterministic results (like threads only read from member variables and writing to them is done in deterministic order or idempotently). Although, for a contrived example, it was more work than I really wanted to do.
I agree, punting is definitely the right course of action. I sort of have a vague intuition for what's going on here, but hammering down the exact details is just so tedious that I don't want to do it.
Although, it is interesting that the AI basically sees threads and blurts out that the problem is impossible, when they're not actually doing anything in this case.
- Filligree 3y agoIt explained the code better than I would have, I think. “Inherently challenging” seems… accurate. I bet that if we’d used a data-parallel approach, e.g. with Rayon, it would have handled that better. As a code assistant, it’s extremely useful if and only if you can check its work. And know how to prompt it.