docs.rs failed to build piying-0.1.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
piying-0.1.1
Piying
Fault-tolerant async actors built on Tokio.
Piying is a fork of Kameo by tqwewe.
Why fork?
- Larger production scope — Piying targets real-time networked games and other latency-sensitive distributed systems, driving changes to codec flexibility, networking, and error handling that go beyond upstream's focus.
- AI-generated code welcome — the upstream project does not accept AI-generated contributions. Piying has no such restriction.
Key differences from upstream
- Pluggable codec system (rkyv, serde, or custom) — decoupled from the core actor framework
PiyingRkyvCodecfor high-performance binary serialization via rkyv- Various networking and swarm improvements for production P2P use
Upstream features (inherited)
- Lightweight async actors on Tokio
- Fault tolerance with supervision strategies
- Flexible messaging (bounded/unbounded channels, backpressure)
- Local and distributed communication via libp2p
- Panic safety and actor isolation
- Type-safe message interfaces
License
Piying is dual-licensed under either:
- MIT License (LICENSE-MIT or http://opensource.org/licenses/MIT)
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
Same as the original Piying project.