English | 简体中文
A family of independent C17 libraries for maintaining the order of changing collections.
LayerKeySort maintains live sequence order as applications insert, remove, and move occurrences. It is not a replacement for one-shot array sorting. The application owns its items and business identities; each product defines its own order-management contract.
New to the Full implementation? These four Chinese-language, source-grounded guides are the main entry point for understanding how Full works internally. They follow a pinned Full v4.1.0 source revision, covering the 16 production C modules and their actual execution paths. They do not describe Mini, and they do not replace the public header or frozen compatibility contract.
- Implementation walkthrough · 从源码理解完整实现 — Start here. Understand why Full maintains live occurrence order rather than merely sorting an array; trace the Block/AVL/Handle structure, insert–move–remove workflows, ManagedOrder, Snapshot, LS1, serialization and restore, and the distinctions between current and legacy code.
- Public API index and key contracts · 64 个公开 API — Find all 64 frozen Full public functions, grouped by purpose and mapped to implementation files. Check required parameters, error outcomes, borrowed ownership, Handle/Cursor lifetimes, callback restrictions, concurrency boundaries, and practical traversal examples before integrating.
- Internal algorithms and data structures · 内部算法详解 — Follow the principal helpers across all 16 production C modules: bounded blocks, implicit AVL maintenance, splitting/merging and redistribution, insertion and move commit paths, bulk reconstruction, allocation diagnostics, stable merges, and V3 LK1 compatibility.
- Validation and source-evidence map · 测试与验证指南 — Locate concrete test functions and assertions for important guarantees; learn the CMake, API/wire fixture, distribution and CI checks, plus how to reproduce them and distinguish examined source from executed tests.
Suggested route: read 1 → 2 → 3 → 4 when studying or maintaining Full; for application integration, start with 2 alongside the Full usage and integration guides. All four are implementation explanations tied to a fixed source SHA, not a claim of exhaustive formal verification.
| Full | Mini | |
|---|---|---|
| Latest published Stable | v4.1.0 | v1.0.0 |
Current main source |
4.1.0 (released update) | 1.0.0 (unchanged) |
| Best fit | More complete ordering and historical workflows | Lightweight local, mutable sequences |
| Live ordering | Relative operations, stable resident handles, comparator-managed option | Relative operations and stable occurrence handles |
| Arbitrary live-order comparison | Available under the Full contract | O(n) worst case |
| Snapshots and persistence | Immutable snapshots, LS1 keys, explicit wire format and restore | Not provided |
| Group and Batch utilities | Provided | Not provided |
| Core implementation | Bounded blocks and balanced index | Independent non-intrusive doubly linked list |
| Public API | 64 functions (Full v4) | 18 functions (Mini v1) |
| Build from this repository | Root CMakeLists.txt |
mini/CMakeLists.txt |
Full and Mini are independent products, not parent-and-child dependencies. Their version numbers, public APIs, compatibility promises and release cycles are separate. Neither library links to the other's production source.
These are capability distinctions, not benchmarks or claims that one product is universally faster. Choose Mini when its narrower contract is enough; choose Full when its additional ordering, snapshot or batch capabilities are required.
| Product | Overview and usage | API / contract | Download |
|---|---|---|---|
| Full | Full README · Integration · Examples | API · V4 frozen contract | Published v4.1.0 Stable · 4.1.0 changes |
| Mini | Mini README · Usage · Example | Mini v1 public contract | Mini v1.0.0 release |
For Mini, use the release's Mini-only source ZIP; GitHub's automatic Source code archive downloads the whole repository. Full publishes a separate two-file amalgamation asset. Follow the chosen product's instructions; the root CMake build remains Full by default.
include/,src/, rootCMakeLists.txt,tests/,benchmarks/and most ofdocs/: Full.mini/: independent Mini implementation, documentation, tests and build.consumers/layer-order-workbench/: Mini consumer application and validation, not Mini production code or a third ordering library..github/, selectedtools/and product-line policy: repository-level integration and product-specific maintenance tooling.
A possible Embedded/MCU edition is only a future concept. No Embedded product, API or release is currently offered.
- Full's published tags use
v*(current published Stable:v4.1.0). - Mini's published tags use
mini-v*(current Stablemini-v1.0.0). - GitHub's repository-wide Latest designation is not a per-product version selector. Use each product's explicit release link.
- Old Full releases and V1–V4 research remain available as history; they are not Mini contracts.
- License: MIT. Each product keeps its own documentation and validation requirements.
Read product-line and release policy (简体中文) and contribution guidelines before cross-product changes.
- Full: Full engineering roadmap and completed three-step optimization cycle, Issue #3; historical problem ledger, Issue #4.
- Mini and its consumers: Mini roadmap, Issue #7.
- Full examples and validation: Full README · Full validation.
- Mini examples and validation: Mini README · Mini development.
Do not infer real-world adoption, universal platform support, or performance superiority from a feature table. Evaluate your application's actual ordering and resource requirements.