Using memory address as ThreadID sometimes gives different threads the same address

還沒有人認領這個 Issue。

In my program, I've created 3 threads and then added them all to a controller thread. However, one thread was never executed (I had print-statements that should have run) and after some debugging I noticed that the size of the controller thread showed 2, when it should have been 3. I did not use thread names. I am only using lambda functions as callback functions for the threads.

Looking at the thread-controllers add function, I saw that a thread is not added when the controller already has a thread with the same ID. I printed the thread-ids of all my threads and it turned out that the 1st and the 3rd thread got the same ID, so the 3rd thread was never added. But this should not be possible as different threads should get different ids?

When I added Serial.println() before and Serial.println(controller.size()) after adding the 3rd thread to the controller, all 3 threads got different IDs. I can not explain this behaviour.

Thus, my conclusion is that using memory address as ThreadID feels unpredictable. Maybe thread id could be substituted by a random number instead? (I did this as a workaround).

從 thread-controllers 的 add 函式以及使用記憶體位址產生 ThreadID 的部分開始。使用三個以 lambda 為基礎的執行緒重現此案例，比較有無呼叫 Serial.println() 時它們的 ID 以及 controller 的大小。當不同的執行緒都被保留，且 controller 始終回報全部三個執行緒時，即表示完成。

由索引模型根據 Issue 內容生成。