Is your feature request related to a problem? Please describe.
When we want to be sure that two variables are equal, no additional components or rows are need.We just need one copy constraint. Current instrument for this __builtin_assigner_exit_check(a == b) uses special component and two table rows
Describe the solution or interface you'd like
Create a function __builtin_assigner_exit_check_eq(a, b) that won't call any blueprint component and just will add one copy constraint to constraint system
Additional context
We widely use this construction in recursive verifier and it costs nearly 200 rows for arithmetics example recursive verifier.
It will be significatly more rows for greater lambda and r parameters.
Is your feature request related to a problem? Please describe. When we want to be sure that two variables are equal, no additional components or rows are need.We just need one copy constraint. Current instrument for this
__builtin_assigner_exit_check(a == b)uses special component and two table rowsDescribe the solution or interface you'd like Create a function
__builtin_assigner_exit_check_eq(a, b)that won't call any blueprint component and just will add one copy constraint to constraint systemAdditional context We widely use this construction in recursive verifier and it costs nearly 200 rows for arithmetics example recursive verifier. It will be significatly more rows for greater
lambdaandrparameters.