159626 2016-07-11 07:34:25 -0700 Implement RunLoop::runNowIfMainThreadOrDispatch 2016-07-21 09:10:26 -0700 1 1 1 Unclassified WebKit WebCore Misc. WebKit Nightly Build Unspecified Unspecified NEW P2 Normal --- 159552 1 pnormand webkit-unassigned ap calvaris cgarcia commit-queue pnormand oldest_to_newest 1209646 0 pnormand 2016-07-11 07:34:25 -0700 +++ This bug was initially created as a clone of Bug #159552 +++ 1210242 1 ap 2016-07-12 16:47:38 -0700 It's been a few times before that I wanted such functionality, but then convinced myself that it shouldn't be added. It would be pretty hard to know about code without knowing whether a block executes right away or races with other code in the function. 1210353 2 cgarcia 2016-07-13 00:39:39 -0700 I'm not sure either, and in any case I don't this would belong to RunLoop class, this could probably be a function on MainThread 1210360 3 calvaris 2016-07-13 01:21:34 -0700 (In reply to comment #1) > It's been a few times before that I wanted such functionality, but then > convinced myself that it shouldn't be added. It would be pretty hard to know > about code without knowing whether a block executes right away or races with > other code in the function. Yes, I understand the concern, which is not that important if you use a debugger and step into the function to see if it is run immediately. We write functions because they are a way to avoid duplicating code. The block: if (isMainThread()) { // do } else RunLoop()... happens a lot and I think it can be simplified in many places. 1210361 4 calvaris 2016-07-13 01:22:46 -0700 (In reply to comment #2) > I'm not sure either, and in any case I don't this would belong to RunLoop > class, this could probably be a function on MainThread I thought of RunLoop because it is the one with the dispatch, but it is true that MainThread could be a better place.