[Issue 6989] Implement toString for std.concurrency.Tid
https://issues.dlang.org/show_bug.cgi?id=6989 --- Comment #8 from github-bugzi...@puremagic.com --- Commit pushed to 2.067 at https://github.com/D-Programming-Language/phobos https://github.com/D-Programming-Language/phobos/commit/69d1348952c9fe56a1d567bfb54ab3138e76a5eb Merge pull request #2772 from quickfur/pr6989_rebase --
[Issue 6989] Implement toString for std.concurrency.Tid
https://issues.dlang.org/show_bug.cgi?id=6989 hst...@quickfur.ath.cx changed: What|Removed |Added Status|NEW |RESOLVED CC||hst...@quickfur.ath.cx Resolution|--- |FIXED --
[Issue 6989] Implement toString for std.concurrency.Tid
https://issues.dlang.org/show_bug.cgi?id=6989 --- Comment #7 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/D-Programming-Language/phobos https://github.com/D-Programming-Language/phobos/commit/69d1348952c9fe56a1d567bfb54ab3138e76a5eb Merge pull request #2772 from quickfur/pr6989_rebase Rebase of PR 2482: Issue 6989 - create a better string representation of Tid --
[Issue 6989] Implement toString for std.concurrency.Tid
https://issues.dlang.org/show_bug.cgi?id=6989 Kevin L changed: What|Removed |Added CC|kevin.lamo...@gmail.com | --
[Issue 6989] Implement toString for std.concurrency.Tid
https://issues.dlang.org/show_bug.cgi?id=6989 --- Comment #6 from Andrej Mitrovic --- (In reply to Sean Kelly from comment #5) > Providing a provably unique > identifier to each thread across the entire run of the program would be > expensive. Isn't starting a thread expensive enough that incrementing a simple counter should be good enough to generate an ID? --
[Issue 6989] Implement toString for std.concurrency.Tid
https://issues.dlang.org/show_bug.cgi?id=6989 Sean Kelly changed: What|Removed |Added CC||s...@invisibleduck.org --- Comment #5 from Sean Kelly --- I think it's reasonable to add a Tid.id property that provides a unique name for a thread. I'd like to allow thread ids to be reused though. Then we could just use the MessageBox address. Providing a provably unique identifier to each thread across the entire run of the program would be expensive. --
[Issue 6989] Implement toString for std.concurrency.Tid
https://issues.dlang.org/show_bug.cgi?id=6989 Kevin L changed: What|Removed |Added CC||kevin.lamo...@gmail.com --- Comment #4 from Kevin L --- *** Issue 13376 has been marked as a duplicate of this issue. *** --
[Issue 6989] Implement toString for std.concurrency.Tid
http://d.puremagic.com/issues/show_bug.cgi?id=6989 Andrej Mitrovic changed: What|Removed |Added Keywords||pull Platform|Other |All AssignedTo|nob...@puremagic.com|andrej.mitrov...@gmail.com OS/Version|Windows |All --- Comment #3 from Andrej Mitrovic 2013-09-17 13:30:06 PDT --- https://github.com/D-Programming-Language/phobos/pull/1582 -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 6989] Implement toString for std.concurrency.Tid
http://d.puremagic.com/issues/show_bug.cgi?id=6989 --- Comment #2 from Andrej Mitrovic 2013-03-25 11:34:26 PDT --- (In reply to comment #1) > Hmm it looks like there isn't such a thing as a cross-platform > thread-identifier (at least not in Druntime). Nevermind, there's actually m_addr, which is a uint on Windows and pthread_t on Posix (a pointer to _opaque_pthread_t). So I think core.thread.Thread should expose a getThreadID() function which returns m_addr, and then Tid can expose this function internally and also use it for toString(). -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 6989] Implement toString for std.concurrency.Tid
http://d.puremagic.com/issues/show_bug.cgi?id=6989 --- Comment #1 from Andrej Mitrovic 2013-01-25 11:42:52 PST --- Hmm it looks like there isn't such a thing as a cross-platform thread-identifier (at least not in Druntime). Personally I like the idea of having named threads, where the name would be stored in a Tid. So you could do things like: spawn("workThread", &func, args); where the first pointer argument is the function. It might help with debugging, e.g. inspecting a Tid of a LinkTerminated exception could tell you which named thread threw the exception. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---