We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When parsing a uint8_t as a yaml using rfl::yaml::write, the value is correctly parsed as dummy_uint8_t=48. Note, 48 is the ASCII code for '0'.
uint8_t
rfl::yaml::write
dummy_uint8_t=48
Reading the value back using rfl::yaml::read<uint8_t> does however yield dummy_uint8_t=0, as 48 is now interpreted as a character instead of a number.
rfl::yaml::read<uint8_t>
dummy_uint8_t=0
The text was updated successfully, but these errors were encountered:
Interesting, thanks for pointing it out. I will take a look.
Sorry, something went wrong.
No branches or pull requests
When parsing a
uint8_t
as a yaml usingrfl::yaml::write
, the value is correctly parsed asdummy_uint8_t=48
. Note, 48 is the ASCII code for '0'.Reading the value back using
rfl::yaml::read<uint8_t>
does however yielddummy_uint8_t=0
, as 48 is now interpreted as a character instead of a number.The text was updated successfully, but these errors were encountered: