-
Notifications
You must be signed in to change notification settings - Fork 124
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
[BUG] u256>
display for non-zero u256
#344
Comments
u256>
display for non-zero u256
u256>
display for non-zero u256
May I take this issue on? |
Is this issue still available? |
Mind if I take this issue? I will do this in 2 days max. Completed basecamp, Nodeguardian quest and starklings, also contributed to OD in Cairo |
Hi, ETA: |
Hi, |
Hi, I’d be thrilled to work on this issue as I have extensive experience with Cairo programming and building decentralized applications on StarkNet. ETA: Looking forward to contributing! |
Is it okay if I tackle this? this will be my first time contributing. |
Could I take a shot at this? |
Hi, I am a proficient blockchain developer, expert in Cairo, Rust, Solidity, Aptos, and web development. I have contributed to various projects like Chainevents and Arkprojects etc. Thank you! |
I'd love to work on this! |
Can I take care of this issue? |
hey sir i would love to work on this issue |
hey @jedstroke , any updates on the issue? |
@metalboyrick I am making a PR soon |
Hi @jedstroke looking forward to your PR, remember that the ODHack will finish on Sunday. |
@jedstroke gm, do let us know if you have any problems ser! |
@metalboyrick there isn't any problems, honestly. I will make the PR soon trust me 🙏🏽 |
Sure, please keep in mind that you need some time window for PR reviews too |
Last day to upload your PR @jedstroke, thank you |
I am done boss @Nadai2010. I am pushing the PR fix shortly. Thank you. |
Issue Overview
u256>
display for non-zerou256
, This will happen to all non-zero type-wrappers. We expect onlyu256 will appear on these cases
Proposed Solutions or Ideas
The text was updated successfully, but these errors were encountered: