Closed Curricane closed 10 months ago
It was a rust issue. ref: https://github.com/rust-lang/rust/pull/100806#issuecomment-1825585534
The only way, aka workaround, as far as I kown, is that use Rust stable channel or use a third-part lib to fix this boundary issue: just like what I have did here: https://github.com/greenhat616/clash-verge/tree/main/backend/delay_timer
str_splitter
to fix this boudary issueit looks like the issue has made it into rust stable -- https://github.com/rust-lang/rust/pull/100806#issuecomment-1871429789
I tried the same diff as you had in https://github.com/greenhat616/clash-verge/commit/dc81e1c0b527defc59ac0b84353977ade760ed52#diff-06f45ed9ebd95944143757cdbc32141be89dc35712bcb01cbf057085538917d4 and that would fix it, although it only works with cargo +nightly
since str_splitter
relies on nightly features
Hi guys, the issue has been fixed in V0.11.5
Describe the bug i can not run
cargo +nightly build
as unsatisfied trait bounds.To Reproduce Steps to reproduce the behavior:
rustc version: rustc 1.76.0-nightly (a1a37735c 2023-11-23) delay_timer commit 69a3867c0981428810bace164159ff4619bcf755
then error will show like:
Expected behavior compile ok
Screenshots
Desktop (please complete the following information):