Contracts & Harnesses for f32::to_int_unchecked
#134
+50
−0
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.
Towards #59
❗ Depends on this WIP Kani Issue, as discussed in this thread in #59
Changes
f32::to_int_unchecked
(located inlibrary/core/src/num/f32.rs
)to_int_unchecked
harnessesto_int_unchecked
of each integer typei8
,i16
,i32
,i64
,i128
,isize
,u8
,u16
,u32
,u64
,u128
,usize
--- 12 harnesses in total.Revalidation
feature/verify-rust-std
branch.<harness_to_run>
can be eithernum::verify
to run all harnesses ornum::verify::<harness_name>
(e.g.checked_f32_to_int_unchecked_i8
) to run a specific harness.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.