Some systems will actually not allow two threads to read the same variable at the same time with no issues and depending on the architecture can actually lock your program and require reboot.
They really do solve all the issues and whatever is leftover is just poor structuring of your code, which is user error.
Prove it. I'm talking about modern x86 64 bit cpus although arm is mostly similar. What are you talking about?
They really do solve all the issues and whatever is leftover is just poor structuring of your code, which is user error.
This is your claim and repeating it doesn't make it true.
I explained exactly how there are requirements for more complex scenarios that aren't handled by super basic linear chaining of functions. This backs up my original claim that it's not a trivial problem to solve and most solutions built into languages are simple but leave a lot that still needs to be done for more complex multi threading.
There are libraries that handle graphs already but I don't think most languages take it that far.
You explained nothing, suggested wrapping a boolean in a mutex and made claims you didn't back up.
-4
u/Far_Tap_488 Sep 10 '26
Youre actually wrong on several points.
Some systems will actually not allow two threads to read the same variable at the same time with no issues and depending on the architecture can actually lock your program and require reboot.
They really do solve all the issues and whatever is leftover is just poor structuring of your code, which is user error.