-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support Primitive Proptests #1363
Labels
[C] Feature / Enhancement
A new feature request or enhancement to an existing feature.
Comments
Replicating linker issue.First, replicate the kani version.
Then run it on the case that replicates this.
|
Info from deep dive: The following is required for kani to work. Currently, we only provide the
Possible |
Code changes implemented to link proptest. After cleanup, we can merge. |
This was referenced Aug 2, 2022
See the following comment for way to integrate proptest w/o significant changes. #1435 (comment) |
Repository owner
moved this from In Progress
to Done
in Kani v0.7
Aug 16, 2022
Repository owner
moved this from In Progress
to Done
in Kani v0.9
Aug 16, 2022
Repository owner
moved this from Blocked
to Done
in Kani v0.8
Aug 16, 2022
This was referenced May 20, 2023
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Requested feature: Support primitive proptests.
Use case: Automatically converting proptests to Kani harnesses allow
us to serve large number of customers like
tokio
that have proptestsimplemented but no Kani harnesses.
Test case:
https://github.com/YoshikiTakashima/kani/tree/yoshi-proptest-primitive/tests/proptest/primitive
Feature Branch on Fork: https://github.com/YoshikiTakashima/kani/tree/yoshi-proptest-primitive/
kani-driver
ata26fbcf makes it purge the old
import. This avoids conflicting imports issue, and allows the
hacked version of proptest to be the only one available.
any<T>
for primitiveT
Arbitrary
andStrategy
Ranges of primitive values.Blocked until linking with-L
is fixed.Hacks/should be fixed before merge:
--extern
import.cargo-kani
is not running the recovery part of modifyingCargo.toml
.The text was updated successfully, but these errors were encountered: