Eli Zaretskii <eliz@gnu.org> schrieb am Sa., 22. Apr. 2017 um 21:09 Uhr:

> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sat, 22 Apr 2017 17:24:44 +0200
> Cc: Philipp Stephani <phst@google.com>
>
> Rather than checking for the main thread, store the owning thread in
> the module structures and check for it.

Can you explain the purpose of these changes and the motivation? A
module shouldn't be restricted to be used by a single thread, should
it?

No, but the thread used to create an environment object, the current Emacs thread, and the current OS thread all have to match. Right now this isn't checked; the current code checks only for the main thread, which isn't correct any more now that there can be more than one interpreter thread.