perf(ext/ffi): Avoid receiving on FFI async work channel when no UnsafeCallback exists #19454
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.
No performance measurements done yet but this makes the FFI event loop middleware avoid
when no FFI workers (callbacks) exist.
When FFI workers do exist this causes an extra immutable borrow. This could maybe be avoided but it would return the vector allocation to FFI-less middleware work.