Revise safety bounds for npcap libraries #25
Merged
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.
npcap
wrapper functions are currently designed to pass mutable references; this adheres to safety constraints but makes async runtimes untenable. This PR changes safety boundaries, opting to passNonNull<Adapter>
rather than&mut Adapter
references to wrapper functions, thereby enabling safe parallel operations to be performed (provided thatUnsafeCell
is correctly added and underlying libraries are appropriately thread-safe).