Skip to content
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

add target_to_bits #16

Merged
merged 11 commits into from
Aug 7, 2024

Conversation

harsh-ps-2003
Copy link
Contributor

@harsh-ps-2003 harsh-ps-2003 commented Aug 1, 2024

Copy link

vercel bot commented Aug 1, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
raito ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2024 3:26pm

@maciejka
Copy link
Collaborator

maciejka commented Aug 1, 2024

Welcome and thanks for contribution.
Please add unit tests. And add comment to the issue #10 so I can assign you.

Copy link
Collaborator

@maciejka maciejka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where are the test cases?
I think it makes sense to squash #15 and #16 into a single pr.

tests/tests.cairo Outdated Show resolved Hide resolved
src/engine.cairo Outdated Show resolved Hide resolved
src/engine.cairo Outdated Show resolved Hide resolved
src/engine.cairo Outdated Show resolved Hide resolved
@maciejka maciejka mentioned this pull request Aug 5, 2024
3 tasks
src/utils.cairo Outdated Show resolved Hide resolved
@maciejka
Copy link
Collaborator

maciejka commented Aug 7, 2024

Please fix conflicts. You can put your functions into validation.cairo for now.

@harsh-ps-2003
Copy link
Contributor Author

harsh-ps-2003 commented Aug 7, 2024

So I should put the target_to_bits and vice versa (with the helper functions) in validation.cairo for now. Basically dump all the changes into a single file? Or maybe keep a separate utils.cairo file? @maciejka

@maciejka
Copy link
Collaborator

maciejka commented Aug 7, 2024

So I should put the target_to_bits and vice versa (with the helper functions) in validation.cairo for now. Basically dump all the changes into a single file? Or maybe keep a separate utils.cairo file? @maciejka

keep utils separate

@maciejka
Copy link
Collaborator

maciejka commented Aug 7, 2024

Fix fmt and tests, please.

maciejka

This comment was marked as duplicate.

Copy link
Collaborator

@maciejka maciejka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are still compilation errors

@maciejka maciejka merged commit 097fb81 into keep-starknet-strange:main Aug 7, 2024
5 checks passed
@harsh-ps-2003 harsh-ps-2003 deleted the target_to_bits branch August 8, 2024 01:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants