Development guidelines for the rust-skiplist project, covering testing, module references, formatting, and error handling conventions.
Guidelines for contributing to the rust-skiplist project, a skiplist implementation in Rust.
Always use `cargo nextest run` to execute tests instead of the standard `cargo test` command. Nextest provides faster, more reliable test execution.
When referencing modules within the same crate, prefer absolute paths using `crate::` over relative paths with `super::`.
**Preferred:**
```rust
use crate::module::function;
```
**Avoid:**
```rust
use super::module::function;
```
Format your code using the nightly Rust formatter:
```bash
cargo +nightly fmt
```
Always run this before committing changes to ensure consistent code style across the project.
Avoid introducing panics where possible. When a panic is unavoidable:
**Example:**
```rust
// Preferred
let value = option.expect("Configuration must be set before initialization");
// Avoid
let value = option.unwrap();
```
1. Run tests with `cargo nextest run`
2. Use `crate::` for internal module references
3. Format code with `cargo +nightly fmt`
4. Minimize panics; prefer `expect()` over `unwrap()`
Leave a review
No reviews yet. Be the first to review this skill!
# Download SKILL.md from killerskills.ai/api/skills/rust-skiplist-development/raw