simstring_rust 0.3.4

A native Rust implementation of the SimString algorithm
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

---
name: Pull Request
about: Propose a change to the project
title: "feat(scope): describe your change"
labels: ""
assignees: ""

---

**Description**

<!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. -->

**Fixes** (issue)

**Type of change**

<!-- Please update the title of your PR to match the type of change. The title will be used for the commit message and the changelog. -->
<!---->
<!-- The `(scope)` is optional and refers to the part of the codebase you're changing (e.g., `feat(search)`, `fix(ci)`). -->

<!-- - [ ] `fix`: A bug fix -->
<!-- - [ ] `feat`: A new feature -->
<!-- - [ ] `feat!`: A breaking change -->
<!-- - [ ] `docs`: Documentation only changes -->
<!-- - [ ] `chore`: Changes to the build process or auxiliary tools -->
<!-- - [ ] `refactor`: A code change that neither fixes a bug nor adds a feature -->
<!-- - [ ] `perf`: A code change that improves performance -->
<!-- - [ ] `test`: Adding missing tests or correcting existing tests -->
<!-- - [ ] `style`: Changes that do not affect the meaning of the code -->
<!-- - [ ] `ci`: Changes to our CI configuration files and scripts -->
<!-- - [ ] `revert`: Reverts a previous commit -->

**How Has This Been Tested?**

<!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. -->

- [ ] Test A
- [ ] Test B

**Checklist:**

- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] Any dependent changes have been merged and published in downstream modules