Yeah, I should clarify that by 'async' I meant any call that 'behind the scenes' sends a message to a process, which makes it suddenly non-blocking and can have consequences like race conditions.
Comments
Log in with your Bluesky account to leave a comment
In that case I think is basically a different problem because processes handle messages sequentially anyways. If the outcome of the message is that the current process receives another one that would still be processed afterwards. I am not sure how knowing it upfront would change the final behaviour
Comments