-
-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement i128 and u128. #284
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Extending the format string is a breaking change so this needs to wait until v0.2.0 but I'll mark this as approved.
i128::min_value() | ||
); | ||
|
||
defmt::info!( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you also test here that we can format u128
and i128
values using the {:?}
format specifier?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it ok now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, looks good; thanks! I'll re-approve the PR but it will need a rebase before it can be merged.
* expand test to include `i64` and `i128` types
Use the new i128 argument in qemu example `log`. Please **note** that this currently leads to "defmt version mismatch" when executing the log binary.
The change updates the `log.rs` program to log i128 type. Co-authored-by: Brigitte <brigitte.markmann@asquera.de>
b60c402
to
c13f676
Compare
Awesome, feel free to squash and merge! |
Closes #199