2210: Tracing printouts for FFI calls #2211
Open
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.
Added the
uniffi:ffi-trace
feature. If enabled, UniFFI will printout tracing-level logs for FFI calls. I hooked up the futures code to this, in the future we could also log more stuff. Lowering/lifting/cloning arcs is the first example that comes to mind.To see tracing, use the
--features=ffi-trace
when running a tests, for example:cd fixtures/futures/src
cargo test --features=ffi-trace
Here's an example of the tracing printouts when running tests from the futures fixtures: