Audit preparedness: implement unit tests #5362
Assignees
Labels
enhancement
New feature or request
Comments
This was referenced Jun 28, 2024
8 tasks
github-merge-queue bot
pushed a commit
that referenced
this issue
Jul 25, 2024
# Description TODO - [x] Make note to finish slice test after `pop_front` issue: #5462 - [x] Refactor `any::<T>()` - [x] Make issues for failing tests ## Problem\* Part of #5362 ## Summary\* Simple combinator-based parsing tests for control flow. - Originally designed for slices, but adapted to arrays by emulating slices as bounded vectors ```rust struct Bvec<T, let N: u32> { inner: [T; N], // elements at indices < offset are zero offset: u32, // elements at indices >= len are zero len: u32, } ``` ## Additional Context This code is hacky, but let me know if any parts are worth cleaning up for the stdlib, e.g. `reverse_array`. ## Documentation\* Check one: - [x] No documentation needed. - [ ] Documentation included in this PR. - [ ] **[For Experimental Features]** Documentation to be submitted in a separate PR. # PR Checklist\* - [x] I have tested the changes locally. - [x] I have formatted the changes with [Prettier](https://prettier.io/) and/or `cargo fmt` on default settings. --------- Co-authored-by: jfecher <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Given list of unit tests from: #5361
Implement those unit tests.
Splitting list into sub-issues:
Sub-issues:
Happy Case
Implement unit tests for all key cases in the omnibus issue: #5173
Project Impact
None
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered: