read-only 0.1.1

Read-only field exposure and safe composition helpers via proc macros
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

# AGENTS.md

## Commands

```sh
# Build
cargo build

# Test
cargo test
cargo test --test compile

# Miri (UB detection for unsafe code in read-only crate)
cargo +nightly miri test --test miri

# Coverage (allow one known uncovered artifact)
cargo llvm-cov --workspace --all-features --summary-only --fail-uncovered-lines 1 --fail-uncovered-regions 1

# Lint
cargo clippy --all-targets --all-features

# Format
cargo fmt --all

# Check
cargo check
```

## Conventions

- Run `cargo fmt` and `cargo clippy` before committing.
- Add macro compile tests under `tests/macro/` for proc macro changes.
- Publish order matters: `read-only-derive` must be published before
  `read-only`, because the public crate depends on the derive crate as a
  versioned proc-macro dependency.
- Keep `CHANGELOG.md` in the [Keep a Changelog](https://keepachangelog.com/en/1.1.0/)
  format, using the standard section headings such as `Added` and `Changed`.
  Include behavior- or API-relevant changes there; do not include
  documentation-only or test-only updates.
- Prefer upstream documentation for re-exported public items when that behavior
  is intentionally delegated upstream.
- Keep the public API minimal and well-documented.