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
Currently, when printing an integer, it is converted to a string via format_field_string even though we track it as an integer in the program boundary. These should be printed as normal integers.
Happy Case
Using println(f"{}", 1) should print 1 instead of 0x01.
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response
The text was updated successfully, but these errors were encountered:
I'd like for us to do this for fields as well to be honest. If users want a hex representation we should represent this through the string formatting options.
When I get a tiny bit more bandwidth (trying to stay laser focused on ZK Fog of War Chess and EPF right now) I'll have a crack at a PR for this, may be 1 or 2 weeks until I start having said crack though.
It'd probably be useful to have other format specifiers too e.g. integer to ASCII as in my script.
Problem
Currently, when printing an integer, it is converted to a string via
format_field_string
even though we track it as an integer in the program boundary. These should be printed as normal integers.Happy Case
Using
println(f"{}", 1)
should print1
instead of0x01
.Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response
The text was updated successfully, but these errors were encountered: