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
Doing the recent refactor #29 was painful because all the different circuit and iterator types needed to be changed. I think it is better to have these types be generic over the Plain and Gate type, but wen can increase the usability and maintainability by introducing type aliases of the form
which allows us to write CircuitP<BooleanGMW> instead of the current Circuit<bool, BooleanGate>. This retains the flexibility, the underlying types are not changed, but increases usability and maintainability for those places where we can bound the circuit by a protocol (of which there are many).
The text was updated successfully, but these errors were encountered:
Doing the recent refactor #29 was painful because all the different circuit and iterator types needed to be changed. I think it is better to have these types be generic over the Plain and Gate type, but wen can increase the usability and maintainability by introducing type aliases of the form
which allows us to write
CircuitP<BooleanGMW>
instead of the currentCircuit<bool, BooleanGate>
. This retains the flexibility, the underlying types are not changed, but increases usability and maintainability for those places where we can bound the circuit by a protocol (of which there are many).The text was updated successfully, but these errors were encountered: