nim-api-design

分类: 内容与多媒体 | 上传者: planetis-m | 下载: 0 | 版本: v1.0（最新）

为库和模块设计清晰的公共 Nim API，包括导出类型、构造函数、查找函数、错误契约和容器样式接口。在创建或查看 Nim 库 API、设计导出的模块表面或决定调用者应如何构建、访问和验证数据时使用。

更新日志: Source: GitHub https://github.com/planetis-m/skills

目录结构

当前层级: tree/master/nim-api-design/

📁 references/
- 📄 accessor_pair.md 1.5 KB
- 📄 collection_accessors.md 2.1 KB
- 📄 constructors.md 1.0 KB
- 📄 distinct_types.md 1.0 KB
- 📄 parameter_and_result_shapes.md 1.6 KB
- 📄 representation_default.md 733 B
📄 SKILL.md 5.3 KB

SKILL.md

---
name: nim-api-design
description: Design clear public Nim APIs for libraries and modules, including exported types, constructors, lookup functions, error contracts, and container-style interfaces. Use when creating or reviewing a Nim library API, designing an exported module surface, or deciding how callers should construct, access, and validate data.
---

# Nim API Design

## Preamble

Use this skill when designing or reviewing a public Nim API.
Default to plain data, one clear surface, and names that match the standard library.
Reference examples live in `references/`.

## Rules

### Public shape

- Prefer plain `object` types for public data models.
- Use `ref object` only when identity, aliasing, shared mutation, graph structure, or handle lifetime is part of the contract.
- Export one primary public representation per concept.
- Prefer procs, overloads, generics, and iterators. Do not default to methods or runtime dispatch for ordinary APIs.
- Use named `object` types for public semantic data.
- Use tuples only for local glue or iterator yields such as `(key, val)`.
- Reuse stdlib names when the behavior matches: `len`, `contains`/`hasKey`, `[]`, `[]=`, `items`/`mitems`, `pairs`/`mpairs`, `incl`/`excl`, `push`/`pop`.

### Contracts

- Keep constraints in types. Use `Natural`, `Positive`, ranges, enums, sets, and `distinct` types instead of weakening to `int` and re-checking manually.
- Use `distinct` when two values share a base type but must not mix.
- Use `func` for pure query operations when purity is part of the public contract.
- Use `{.raises.}` only when it keeps the public exception surface clear and easy to maintain.

### Constructors and conversions

- Value types use `initX()` and return `T`.
- Ref types use `newX()` and return `ref T`.
- Use one `toX()` name for common conversions. Overload on input type.
- Accept `openArray` for batch inputs when callers naturally have arrays, seqs, or literals.
- Keep the zero-argument path simple with sensible defaults.

### Lookup surface

- Separate required lookup from optional lookup.
- A required lookup raises one specific catchable exception. It does not return a silent default.
- An optional lookup uses an explicit safe path such as `contains`, `hasKey`, `getOrDefault`, or `Option[T]`.
- If several accessors fail the same way, route the failure through one private `{.noinline, noreturn.}` helper.

### Borrowed and mutable access

- Use `lent T` for read accessors that return storage owned by the receiver.
- Add `var T`, `mitems`, or `mpairs` only when caller mutation is part of the API.
- Do not expose scalar `var` accessors such as `var int`, `var bool`, or enum fields from internal state.
- In `lent` and `var` accessors, return directly from storage. Do not route through a temp local.

### Public boundary

- Export only the stable surface. Keep helpers private.
- Use descriptive public names.
- In user code, gate version-specific API with `when (NimMajor, NimMinor) >= (x, y)`. Do not use stdlib-internal `{.since.}`.
- Treat paired value/ref APIs and patterns like `withValue` as opt-in compatibility choices, not defaults.

## Workflow

1. Choose the representation.
   Start with a plain `object`. Switch to `ref object` only if the contract needs identity or aliasing.
2. Name the public types.
   Use named objects for semantic results and `distinct` or range types for domain constraints.
3. Name the constructor surface.
   Use `initX`, `newX`, and `toX` in the stdlib style.
4. Design the lookup surface.
   Provide one strict path for required data and one explicit safe path for optional data.
5. Add borrowed and mutable access.
   Use `lent` for reads into owned storage. Add mutable access only where the caller must edit stored data.
6. Verify the contract.
   Compile normally. If you use `lent` or `var` accessors, verify the borrow compiles. If you use `func`, make sure the body stays pure. If you gate by Nim version, use `when` guards.

## Common Mistakes

| Mistake | Why it is wrong |
|---------|------------------|
| Starting with `ref object` for plain data | It adds aliasing and shared mutation where the API does not need them |
| Defaulting to methods or runtime dispatch | It hides behavior behind runtime polymorphism when a proc surface is simpler and clearer |
| Weakening `Natural` or `Positive` to `int` and re-checking manually | It throws away a stronger type-level contract |
| Returning a silent default for required data | It hides missing-data bugs |
| Exporting scalar `var` accessors | It leaks mutable internal state |
| Returning a `lent` or `var` result through a temp local | ORC rejects the borrow because the temp escapes |

## References

- `references/representation_default.md` — Plain `object` default and `ref object` only when aliasing is required
- `references/constructors.md` — `initX`, `newX`, and `toX` constructor patterns
- `references/collection_accessors.md` — One coherent container surface with stdlib-style names
- `references/accessor_pair.md` — Minimal borrowed and mutable accessor pair with one shared error helper
- `references/distinct_types.md` — Domain types with `distinct` and borrowed operations
- `references/parameter_and_result_shapes.md` — Parameter defaults, options objects, and named result objects

## Changelog

- 2026-04-08: Initial verified skill.
- 2026-04-11: Added value-vs-ref claims and `func` purity tests.

登录后下载/点赞/收藏 ❤ 30 | ★ 0

nim-api-design

目录结构

SKILL.md

举报内容

提示