privacy-scaling-explorations / zk-kit.rust / 15545801854 / 1
90%
main: 90%

DEFAULT BRANCH: main
Ran
Files 10
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 89.757% (+0.1%) from 89.651%
15545801854.1

push

github

web-flow 
Add missing `index_of()` fn (#67)

<!-- Please refer to our CONTRIBUTING documentation for any questions on
submitting a pull request. -->
<!-- Provide a general summary of your changes in the Title above. -->

## Description
This PR aims to add an `index_of()` fn to `IMT` impl to mirror the TS
implementation. The function takes a `leaf` and returns an
`Option<usize>` that evaluate to `Some(idx)` where `idx` is the index of
the `leaf` or `None` when the `leaf` does not exists in the `IMT`.

<!-- Describe your changes in detail. -->
<!-- You may want to answer some of the following questions: -->
<!-- What kind of change does this PR introduce?** (Bug fix, feature,
docs update, ...) -->
<!-- What is the current behavior?** (You can also link to an open issue
here) -->
<!-- What is the new behavior (if this is a feature change)? -->
<!-- Does this PR introduce a breaking change?** (What changes might
users need to make in their application due to this PR?) -->

## Checklist

<!-- Please check if the PR fulfills these requirements. -->

- [x] I have read and understand the [contributor
guidelines](https://github.com/privacy-scaling-explorations/zk-kit.rust/blob/main/CONTRIBUTING.md)
and [code of
conduct](https://github.com/privacy-scaling-explorations/zk-kit.rust/blob/main/CODE_OF_CONDUCT.md).
- [x] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [x] My changes generate no new warnings
- [x] I have run `yarn style` without getting any errors
- [x] I have added tests that prove my fix is effective or that my
feature works
- [x] New and existing unit tests pass locally with my changes

> [!IMPORTANT]
> We do not accept minor grammatical fixes (e.g., correcting typos,
rewording sentences) unless they significantly improve clarity in
technical documentation. These contributions, while appreciated, are not
a priority for merging. If there is a grammatical mistake, please feel
free to message the team.

1586 of 1767 relevant lines covered (89.76%)

180281.6 hits per line

Source Files on job 15545801854.1