- Manage dependencies in the workspace
Cargo.toml. - Use the
panic!macro instead of falling back to meaningless dummy values or no-op implementations. - Use the
2024edition. - Keep the code free of compiler warnings and Clippy lints.
mise run clippyruns-D warnings, so any warning or lint fails it. - Import every item you name. A
crate::orsuper::path goes in auseitem at the top of the module; where the item is read, write its name.use crate::elaborator::sem::Ty;thenTy, nevercrate::elaborator::sem::Tyinline. Alias a collision (use crate::ast::Ty as AstTy;) rather than spelling the path out. A hook refuses an edit that writes one inline, andmise run check-rust-pathsgates the rest. - Avoid wildcard match arms (
_ => ...) unless absolutely necessary.
Workspace-specific Rust rules that override common habits: panic instead of dummy or no-op fallbacks, no wildcard match arms, dependencies managed in the workspace Cargo.toml, 2024 edition, zero warnings and clippy lints. Read before writing or editing Rust (.rs) code.
- 1 file
- 1.1 KB
- Updated 4 weeks ago
- GitHub
Ask your Agent
Use this Skill: https://skilld.dev/gh/wado-lang/wado/rust
This session only. Nothing lands on disk.
≈69 tokens always: the name and description. ≈200 when used: this file.
Source: SKILL.md on GitHub
Third-party checks
No third-party reports yet.
Provenance
Signed by skilld at 323789e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub yesterday.
Activeupdated 4 weeks ago