-
Notifications
You must be signed in to change notification settings - Fork 103
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
Upgrade to Cairo 2.5.3
and other refactors
#271
Conversation
Sure
El El jue, 1 feb 2024 a la(s) 8:52, Lucas @ StarkWare <
***@***.***> escribió:
… put #272 <#272>
and #270 <#270>
in the same PR as this one
—
Reply to this email directly, view it on GitHub
<#271 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIKSPDJKST4HODF4YTVKK3YROT3JAVCNFSM6AAAAABCTP4XPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRRGUYTINBSGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
f625f61
to
1898a08
Compare
@LucasLvy done |
2.5.0
and other refactors2.5.3
and other refactors
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you also change all the assert(x == y, 'xyz')
into assert_eq!(x, y, "xyz");
you can use a regex for that
Revert changes
bbedc21
to
e49bda0
Compare
I would wait for snfoundry to be ready before doing it in library code because error message catching infra isn't fully implemented yet foundry-rs/starknet-foundry#1627 |
65d5ede
to
26e9b19
Compare
26e9b19
to
7ee011b
Compare
done as much as i could, it failed in many places (out of gas, formatter unimplemented, other weird errors) |
Let's not care about other tools, if someone wants to use it with foundry they'll use the old version |
well we at argent would like to use the latest alexandria with foundry, but the assert! macros feel a bit too unstable to be shipped to mainnet |
Pull Request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this introduce a breaking change?
Other information