cleanup a typecast ambiguity due to new API

Rust can't tell how to cast some u32_le into u32/usize automatically
due to confusion with the num_derive trait, so we have to explicitly
specify a chain of typecasts to clean up the conflict with the
new rkyv
This commit is contained in:
bunnie 2024-09-22 14:24:59 +08:00
parent 1b0fa6e04b
commit 0fbca1cd4d

View file

@ -845,7 +845,9 @@ fn main() -> ! {
match xns.request_connection_blocking(kr.server_name.as_str()) { match xns.request_connection_blocking(kr.server_name.as_str()) {
Ok(cid) => { Ok(cid) => {
listener_conn = Some(cid); listener_conn = Some(cid);
listener_op = Some(kr.listener_op_id as usize); listener_op = Some(<usize as From<usize>>::from(<u32 as From<u32>>::from(
kr.listener_op_id.into(),
) as usize));
} }
Err(e) => { Err(e) => {
log::error!("couldn't connect to listener: {:?}", e); log::error!("couldn't connect to listener: {:?}", e);
@ -860,7 +862,7 @@ fn main() -> ! {
match xns.request_connection_blocking(kr.server_name.as_str()) { match xns.request_connection_blocking(kr.server_name.as_str()) {
Ok(cid) => { Ok(cid) => {
raw_listener_conn = Some(cid); raw_listener_conn = Some(cid);
raw_listener_op = Some(kr.listener_op_id as u32); raw_listener_op = Some(<u32 as From<u32>>::from(kr.listener_op_id.into()));
} }
Err(e) => { Err(e) => {
log::error!("couldn't connect to listener: {:?}", e); log::error!("couldn't connect to listener: {:?}", e);
@ -876,7 +878,10 @@ fn main() -> ! {
match xns.request_connection_blocking(kr.server_name.as_str()) { match xns.request_connection_blocking(kr.server_name.as_str()) {
Ok(cid) => { Ok(cid) => {
observer_conn = Some(cid); observer_conn = Some(cid);
observer_op = Some(kr.listener_op_id as usize); observer_op = Some(<usize as From<usize>>::from(<u32 as From<u32>>::from(
kr.listener_op_id.into(),
)
as usize));
} }
Err(e) => { Err(e) => {
log::error!("couldn't connect to observer: {:?}", e); log::error!("couldn't connect to observer: {:?}", e);