mirror of
https://github.com/wolfpld/tracy.git
synced 2024-11-10 10:41:50 +00:00
54ee3d8a94
These are extremely useful for ecosystems such as Rust. There are a couple of reasons why: 1. Rust strongly advises against relying on life before/after main, as it is difficult to reason about. Most users working in Rust will generally be quite surprised when encountering this concept. 2. Rust and its package manager makes it easy to use packages (crates) and somewhat less straightforward to consider the implications of including a dependency. In case of the `rust_tracy_client` set of packages, I currently have to warn throughout the documentation of the package that simply adding a dependency on the bindings package is sufficient to potentially accidentally broadcast a lot of information about the instrumented binary to the broader world. This seems like a major footgun given how easy is it to forget about having added this dependency. Ability to manually manage the lifetime of the profiler would be a great solution to these problems. |
||
---|---|---|
.. | ||
tracy_concurrentqueue.h | ||
tracy_rpmalloc.cpp | ||
tracy_rpmalloc.hpp | ||
TracyAlloc.cpp | ||
TracyArmCpuTable.hpp | ||
TracyCallstack.cpp | ||
TracyCallstack.h | ||
TracyCallstack.hpp | ||
TracyDebug.hpp | ||
TracyDxt1.cpp | ||
TracyDxt1.hpp | ||
TracyFastVector.hpp | ||
TracyLock.hpp | ||
TracyProfiler.cpp | ||
TracyProfiler.hpp | ||
TracyRingBuffer.hpp | ||
TracyScoped.hpp | ||
TracySysTime.cpp | ||
TracySysTime.hpp | ||
TracySysTrace.cpp | ||
TracySysTrace.hpp | ||
TracySysTracePayload.hpp | ||
TracyThread.hpp |