You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've started rewriting Iggy.rs into monoio runtime, as I'd like to see the potential benefits of io_uring along with TPC model (and compare the results with existing Tokio runtime), and I've found the following bug? in this line:
It does return u16 instead of u128, while read_i128_le returns i128 - is there any reason why u128 isn't available? We use this for message IDs (e.g. UUID) and would like to stick to u128 if possible.
Cheers and thanks for the great work on this runtime!
The text was updated successfully, but these errors were encountered:
spetz
changed the title
read_u128_le() returns u16 instead of u128`read_u128_le() returns u16 instead of u128Apr 16, 2024
Hello,
I've started rewriting Iggy.rs into monoio runtime, as I'd like to see the potential benefits of
io_uring
along with TPC model (and compare the results with existing Tokio runtime), and I've found the following bug? in this line:monoio/monoio/src/io/async_read_rent_ext.rs
Line 73 in 5c007db
It does return
u16
instead ofu128
, whileread_i128_le
returnsi128
- is there any reason whyu128
isn't available? We use this for message IDs (e.g. UUID) and would like to stick tou128
if possible.Cheers and thanks for the great work on this runtime!
The text was updated successfully, but these errors were encountered: