purecv 0.1.4

A pure Rust, high-performance computer vision library focused on safety and portability.
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
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92

# Contributing to purecv

Thank you for your interest in contributing to `purecv`! By following these guidelines, you help keep the project clean, organized, and easy to maintain.

## Pull Request Workflow

To contribute to the project, please follow these steps:

1. **Sync with the `dev` branch**: Ensure your local copy is up to date before starting new work.
   ```powershell
   git checkout dev
   git pull origin dev
   ```
2. **Create a new branch**: Create a descriptive branch starting from `dev`.
   ```powershell
   git checkout -b your-branch-name
   ```
3. **Develop and Test**: Make your changes and ensure they pass all tests (see the [Testing](#testing) section).
4. **Submit the Pull Request**: Open a PR against the `dev` branch of the main repository.

> **Important**: All PRs must be made against the `dev` branch. The `main` branch is reserved exclusively for stable releases.

## Testing

Before submitting a commit or a Pull Request, it is essential to verify that the code works correctly and adheres to the project's quality standards.

Run the following commands in the project root:

* **Run tests**:
  ```powershell
  cargo test
  ```
* **Check formatting**:
  ```powershell
  cargo fmt -- --check
  ```
* **Run linting with Clippy**:
  ```powershell
  cargo clippy -- -D warnings
  ```

If you add a new feature, make sure to include appropriate tests in `src/**/tests.rs` or as integration tests.

## Commit Message Conventions

To maintain a clean and automated release history, this project strictly adheres to the [Conventional Commits](https://www.conventionalcommits.org/) specification.

All Pull Requests will be squashed and merged. Please ensure your PR titles and commit messages follow this format:

`<type>(<optional scope>): <description>`

### 1. Allowed Types
* **`feat`**: A new feature or core algorithm implementation.
* **`fix`**: A bug fix.
* **`perf`**: A code change that improves performance.
* **`doc`**: Documentation-only changes.
* **`refactor`**: A code change that neither fixes a bug nor adds a feature (e.g., restructuring).
* **`test`**: Adding missing tests or correcting existing ones.
* **`style`**: Changes that do not affect the meaning of the code (formatting, missing semi-colons, etc.).
* **`chore`**: Changes to the build process, CI configuration, or auxiliary tools.

### 2. Project-Specific Scopes
To help us automatically categorize changes in our Changelog, please use one of the following scopes when applicable:
* **`simd`**: Manual vectorization or SIMD-specific optimizations (via Pulp).
* **`wasm`**: WebAssembly and Emscripten target adjustments or optimizations.
* **`parallel`**: Concurrency implementations (e.g., Rayon).
* **`core`**: Core matrix operations, memory layout, or foundational structs.
* **`imgproc`**: Image processing algorithms, filters, and color conversions.

### 3. Examples
* `feat(simd): implement vectorized absolute difference`
* `perf(wasm): optimize memory allocation for emscripten builds`
* `fix(core): resolve out-of-bounds error in matrix transpose`
* `doc: update README with parallel execution benchmarks`

If your PR introduces a breaking change, please include `BREAKING CHANGE:` in the footer or append a `!` after the type/scope (e.g., `feat(core)!: change Matrix internal layout`).

## Creating Issues

Before creating a new issue, please search the [existing issues](https://github.com/kalwalt/purecv/issues) to see if it has already been reported.

When creating an issue, please provide as much information as possible:
* **For Bug Reports**: Include a clear description of the bug, steps to reproduce it, the expected behavior, and any relevant error messages or logs.
* **For Feature Requests**: Explain the purpose of the feature, why it is needed, and how it should work.

## Reporting Bugs and Feature Requests

If you encounter a bug or have an idea for a new feature, we invite you to open an [Issue](https://github.com/kalwalt/purecv/issues). Please be as detailed as possible in the description to help us resolve the issue quickly.

## Code of Conduct

We adopt the [Contributor Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md) to promote an inclusive and respectful environment for all contributors.