Initial.

Author: Caia-Tech

.github/workflows/ci.yml

@@ -0,0 +1,107 @@
+name: CI
+
+on:
+  push:
+    branches: [ main, master ]
+  pull_request:
+    branches: [ main, master ]
+
+env:
+  CARGO_TERM_COLOR: always
+
+jobs:
+  test:
+    name: Test
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        rust:
+          - stable
+          - beta
+          - nightly
+    steps:
+    - uses: actions/checkout@v3
+    
+    - name: Install Rust
+      uses: actions-rs/toolchain@v1
+      with:
+        profile: minimal
+        toolchain: ${{ matrix.rust }}
+        override: true
+    
+    - name: Cache dependencies
+      uses: actions/cache@v3
+      with:
+        path: |
+          ~/.cargo/registry
+          ~/.cargo/git
+          target
+        key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
+    
+    - name: Build
+      run: cargo build --verbose
+    
+    - name: Run tests
+      run: cargo test --verbose
+    
+    - name: Run property tests
+      run: cargo test --test property_tests --verbose
+    
+    - name: Check formatting
+      run: cargo fmt -- --check
+      if: matrix.rust == 'stable'
+    
+    - name: Run clippy
+      run: cargo clippy -- -D warnings
+      if: matrix.rust == 'stable'
+
+  benchmark:
+    name: Benchmark
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+    
+    - name: Install Rust
+      uses: actions-rs/toolchain@v1
+      with:
+        profile: minimal
+        toolchain: stable
+        override: true
+    
+    - name: Cache dependencies
+      uses: actions/cache@v3
+      with:
+        path: |
+          ~/.cargo/registry
+          ~/.cargo/git
+          target
+        key: ${{ runner.os }}-cargo-bench-${{ hashFiles('**/Cargo.lock') }}
+    
+    - name: Run benchmarks
+      run: cargo bench --no-run
+
+  coverage:
+    name: Code Coverage
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+    
+    - name: Install Rust
+      uses: actions-rs/toolchain@v1
+      with:
+        profile: minimal
+        toolchain: stable
+        override: true
+        components: llvm-tools-preview
+    
+    - name: Install cargo-llvm-cov
+      uses: taiki-e/install-action@cargo-llvm-cov
+    
+    - name: Generate code coverage
+      run: cargo llvm-cov --all-features --workspace --lcov --output-path lcov.info
+    
+    - name: Upload coverage to Codecov
+      uses: codecov/codecov-action@v3
+      with:
+        files: lcov.info
+        fail_ci_if_error: false

.gitignore

@@ -0,0 +1,48 @@
+# Generated by Cargo
+# will have compiled files and executables
+/target/
+debug/
+target/
+
+# Remove Cargo.lock from gitignore if creating an executable, leave it for libraries
+# More information here https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
+Cargo.lock
+
+# These are backup files generated by rustfmt
+**/*.rs.bk
+
+# MSVC Windows builds of rustc generate these, which store debugging information
+*.pdb
+
+# IDE specific files
+.idea/
+*.iml
+.vscode/
+*.swp
+*.swo
+*~
+
+# OS specific files
+.DS_Store
+Thumbs.db
+
+# Benchmark results
+/target/criterion/
+
+# Property test regressions
+**/*.proptest-regressions
+
+# Debug binaries
+debug_*
+
+# Coverage reports
+*.profraw
+*.profdata
+/coverage/
+
+# Documentation build
+/target/doc/
+
+# Temporary files
+*.tmp
+temp/

CONTRIBUTING.md

@@ -0,0 +1,127 @@
+# Contributing to Rust LeetCode Solutions
+
+Thank you for your interest in contributing! This guide will help you add new problems or improve existing solutions.
+
+## Adding a New Problem
+
+### 1. File Structure
+
+Create a new file in the appropriate difficulty folder:
+- `src/easy/problem_name.rs`
+- `src/medium/problem_name.rs`
+- `src/hard/problem_name.rs`
+
+### 2. Solution Template
+
+```rust
+//! # Problem [NUMBER]: [TITLE]
+//!
+//! [Problem description]
+//!
+//! ## Examples
+//!
+//! ```
+//! [Example input/output]
+//! ```
+//!
+//! ## Constraints
+//!
+//! * [List constraints]
+
+/// Solution for [Problem Name]
+pub struct Solution;
+
+impl Solution {
+    pub fn new() -> Self {
+        Solution
+    }
+
+    /// # Approach 1: [Name] (Optimal/Alternative)
+    /// 
+    /// **Algorithm:**
+    /// 1. [Step 1]
+    /// 2. [Step 2]
+    /// 
+    /// **Time Complexity:** O(?)
+    /// **Space Complexity:** O(?)
+    /// 
+    /// **Key Insight:** [Explain why this works]
+    pub fn method_name(&self, input: Type) -> ReturnType {
+        // Implementation
+    }
+}
+
+#[cfg(test)]
+mod tests {
+    use super::*;
+
+    #[test]
+    fn test_basic_cases() {
+        // Test implementation
+    }
+}
+```
+
+### 3. Requirements
+
+Each solution must include:
+
+- [ ] Problem description with examples
+- [ ] At least one optimal solution
+- [ ] Time and space complexity analysis
+- [ ] Clear explanation of the approach
+- [ ] Comprehensive unit tests
+- [ ] Edge case handling
+
+Bonus points for:
+- [ ] Multiple approach implementations
+- [ ] Benchmark comparisons
+- [ ] Property-based tests
+- [ ] Visual explanations in comments
+
+### 4. Testing
+
+Ensure all tests pass:
+```bash
+cargo test problem_name
+cargo clippy -- -D warnings
+cargo fmt
+```
+
+### 5. Documentation
+
+Add your problem to:
+1. The module file (`src/{difficulty}/mod.rs`)
+2. The README.md problems list
+3. Update the problem count in README
+
+## Code Style
+
+- Use idiomatic Rust patterns
+- Prefer iterators over loops when clearer
+- Use descriptive variable names
+- Add comments for complex logic
+- Format with `cargo fmt`
+
+## Commit Guidelines
+
+- Use clear commit messages
+- Reference the LeetCode problem number
+- Example: `Add Problem #42: Trapping Rain Water with multiple approaches`
+
+## Pull Request Process
+
+1. Fork the repository
+2. Create a feature branch: `git checkout -b add-problem-123`
+3. Commit your changes
+4. Push to your fork
+5. Create a Pull Request with:
+   - Problem number and title
+   - Brief description of approaches implemented
+   - Test coverage confirmation
+
+## Questions?
+
+Feel free to open an issue for discussion before implementing a complex solution.
+
+Thank you for contributing!

Cargo.toml

@@ -0,0 +1,39 @@
+[package]
+name = "rust-leetcode"
+version = "0.1.0"
+edition = "2021"
+authors = ["Rust LeetCode Contributors"]
+description = "Comprehensive LeetCode solutions in Rust with multiple approaches, benchmarking, and property-based testing"
+license = "MIT"
+repository = "https://github.com/yourusername/rust-leetcode"
+readme = "README.md"
+homepage = "https://github.com/yourusername/rust-leetcode"
+documentation = "https://docs.rs/rust-leetcode"
+keywords = ["leetcode", "algorithms", "data-structures", "rust"]
+categories = ["algorithms", "data-structures"]
+
+[dependencies]
+
+[dev-dependencies]
+# Testing framework enhancements
+criterion = "0.5"  # For benchmarking
+proptest = "1.0"   # Property-based testing
+rstest = "0.18"    # Parameterized testing
+
+[[bench]]
+name = "solutions"
+harness = false
+
+[lib]
+name = "rust_leetcode"
+path = "src/lib.rs"
+
+# Enable all lints for clean code
+[lints.rust]
+unsafe_code = "forbid"
+missing_docs = "warn"
+
+[lints.clippy]
+all = "warn"
+pedantic = "warn"
+nursery = "warn"

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Rust LeetCode Solutions
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.