Add tracing mutex support (deprecated branch, ignore/delete this PR!) #11
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.
IGNORE THIS ONE, this is the wrong branch. Refer to #12 for the real PR
As announced in #10, here is my implementation of lockables in the form of mutexes. I decided it would be nicest to wrap the Tracy API in a
TracingMutexstruct (much likeTracingAllocator). This mimicks the intended use of lockables in Tracy for C++ in an idiomatic Zig way.getSrcLoc(..)to re-use source location trick and clean up the flow of code.examples/folder for nicer organization of multiple examples (decided to split the mutex example to not clutter the basic example).Closes #10.