Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For context, see issue #29.
This is my proposed solution as an attempt to write the "proper" PID and TID of the results so that the processes/threads can be differentiated.
std::process::id()
, which "Returns the OS-assigned process identifier associated with this process.", as documented in the Rust official docsstd::thread::current().id()
, which could be problematic, as I've made a hack to convert the debug output to an int, and there's no guarantee that the integer is related to the OS's assigned identifier of the thread. A proper solution would depend on the stabilization ofThreadId::as_u64
. However, as the purpose here is only to uniquely identify a thread(which is already guaranteed by the current API), I don't think this is a major issue.