Hi, thx for awesome crate! Does that crate is production-ready? And whats features of original KCP protocol is missing? I do small test - using client implementation from https://github.com/deepseeksss/tokio_kcp connect to example echo server from that crate and receive some panic, full output:
cargo run --package kcp-rs --example echo
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.06s
Running `target/debug/examples/echo`
Received: Hello KCP!
thread 'main' (115463) panicked at src/kcp.rs:429:28:
attempt to add with overflow
stack backtrace:
0: __rustc::rust_begin_unwind
at /rustc/0febdbab2720dc0360cd294c67db88d6d06580d4/library/std/src/panicking.rs:689:5
1: core::panicking::panic_fmt
at /rustc/0febdbab2720dc0360cd294c67db88d6d06580d4/library/core/src/panicking.rs:80:14
2: core::panicking::panic_const::panic_const_add_overflow
at /rustc/0febdbab2720dc0360cd294c67db88d6d06580d4/library/core/src/panicking.rs:175:17
3: <kcp_rs::kcp::Kcp<echo::UdpOutput>>::update_rtt
at ./src/kcp.rs:429:28
4: <kcp_rs::kcp::Kcp<echo::UdpOutput>>::process_ack
at ./src/kcp.rs:379:18
5: <kcp_rs::kcp::Kcp<echo::UdpOutput>>::input
at ./src/kcp.rs:342:26
6: echo::main
at ./examples/echo.rs:45:37
7: <fn() -> core::result::Result<(), std::io::error::Error> as core::ops::function::FnOnce<()>>::call_once
at /home/user/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Hi, thx for awesome crate! Does that crate is production-ready? And whats features of original KCP protocol is missing? I do small test - using client implementation from https://github.com/deepseeksss/tokio_kcp connect to example echo server from that crate and receive some panic, full output: