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
Currently we have these string conversion functions/mappings (ignoring hex_bits_signed):
hex_bits_signed
hex_bits
bits(N) <-> str
bits_str
bits(N) -> str
dec_str
int -> str
hex_str
This is a bit inconsistent. It would be nice if everything was a mapping, and maybe the naming was a bit more consistent:
str_bits
dec_int
int <-> str
hex_int
I dunno if those are the best names. Anyway making dec_str and hex_str a mapping would be useful in quite a lot of the RISC-V assembly mappings.
assembly
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently we have these string conversion functions/mappings (ignoring
hex_bits_signed
):hex_bits
bits(N) <-> str
bits_str
bits(N) -> str
dec_str
int -> str
hex_str
int -> str
This is a bit inconsistent. It would be nice if everything was a mapping, and maybe the naming was a bit more consistent:
hex_bits
bits(N) <-> str
str_bits
?bits(N) <-> str
dec_int
int <-> str
hex_int
int <-> str
I dunno if those are the best names. Anyway making
dec_str
andhex_str
a mapping would be useful in quite a lot of the RISC-Vassembly
mappings.The text was updated successfully, but these errors were encountered: