No. Here I'm telling the reconciler Job what thread is (going to be) running in. Here is what the documentation for ``job.setThread`` says: *Jobs that use the {@link #ASYNC_FINISH} return code should tell the job what thread it is running in.  This is used to prevent deadlocks.*

But now I have doubts this is the right way to use the API. Rather, I think I should move ``reconciler.setThread(Display.getDefault.getThread())`` inside the ``SWTUtils.asyncExec`` and here I should call ``reconciler.setThread(Thread.getCurrentThread())``

I'm going to do this, unless you disagree.