Public service announcement: steps running in parallel should not be reading, much less modifying, any state directly observable outside those steps. Anything like that needs to happen via tasks.
-
-
Replying to @really_bz @bz_moz
And we so don't have the tools to help spec writers check that we've followed that rule.
1 reply 0 retweets 0 likes -
-
Replying to @really_bz @bz_moz
I think it'd be sufficient to have Bikeshed/Respec recognize member accesses, track them through variable assignments, and enforce that 'in parallel' blocks don't use objects reachable from globals. Something like https://clang.llvm.org/docs/ThreadSafetyAnalysis.html … rather than TSan's dynamic analysis.
1 reply 0 retweets 2 likes
Replying to @jyasskin
This would help a lot, yes. Wouldn't catch everything, but would catch naive mistakes...
2:17 PM - 14 Nov 2019
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.