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
release 0.3.0 references noir_bignum v0.3.3 which has an issue https://github.com/noir-lang/noir-bignum/issues/25. This was resolved in noir_bignum 0.3.4 which is included here in commit 499a7f8 but is not released
See request for release 0.3.5 of noir_bignum- there is an additional compilation issue I won't redetail here. But in order for noir_rsa to compile with aztec-nargo, the non-ascii characters in upstream noir_bignum must be removed from the comments.
Happy Case
Would be nice to have a quick tagged release of noir_rsa 0.3.1 including described bump to noir_bignum 0.3.5 so that we can specify the dependency without local bash scripting to fix/ cloned repos
Afaik you can't patch nargo.toml if you can though pls ignore
Workaround Description
Clone downstream repositories and change dependencies, potentially pushing to forked library if critical
The text was updated successfully, but these errors were encountered:
Problem
release 0.3.0 references noir_bignum v0.3.3 which has an issue
https://github.com/noir-lang/noir-bignum/issues/25
. This was resolved in noir_bignum 0.3.4 which is included here in commit 499a7f8 but is not releasedSee request for release 0.3.5 of noir_bignum- there is an additional compilation issue I won't redetail here. But in order for noir_rsa to compile with aztec-nargo, the non-ascii characters in upstream noir_bignum must be removed from the comments.
Happy Case
Would be nice to have a quick tagged release of noir_rsa 0.3.1 including described bump to noir_bignum 0.3.5 so that we can specify the dependency without local bash scripting to fix/ cloned repos
Afaik you can't patch nargo.toml if you can though pls ignore
Workaround Description
Clone downstream repositories and change dependencies, potentially pushing to forked library if critical
The text was updated successfully, but these errors were encountered: