Add a kani::futures
library containing block_on
#1427
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.
Description of changes:
Following up on #1414, this adds a
kani::block_on
function to drive futures to completion in Kani. Theblock_on
function fromfutures
ortokio
do not work because Kani does not understand the thread primitives these implementations use.Callouts:
I had to add
#[inline]
annotations to work around the linking issue #1425. But inlining makes sense for these functions anyway (they're small and do basically nothing), so this is not a problem.Testing:
How is this change tested? Added a test in
tests/kani/AsyncAwait/main.rs
Is this a refactor change? No
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.