First `re_thread_init()` always fails with `EALREADY` about re HOT 4 CLOSED

BTW, re_global can become dangling since the re context may be deleted by re_thread_close or thread termination. For example, this breaks libre_close.

from re.

For the main thread re_thread_init should not be called, only for additional worker threads.

re_global is needed as fallback for re_thread_enter see https://github.com/baresip/re/wiki/Development-(re-usage)#thread-safety-for-non-re-threads

from re.

There is no "main thread" in our case. There can be any number of threads that are running separate instances of event loop.

re_global is needed as fallback for re_thread_enter

My suggestion is to remove the fallback. Require the caller of re_thread_enter specify the re instance he wants to use until re_thread_leave. Ultimately, there would be no global state in libre (other than TLS, perhaps), and the caller would be able to explicitly create and destroy re contexts and specify the context he wants to operate on. Basically, this would properly allow for multi-instance use of libre.

from re.

Removing the fallback would break existing applications, like the baresip android app. Can you try this PR: #404

from re.