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.

Sign up for GitHub

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

Jump to bottom

Migrate toAllocatedScalar in public API instead of Variable #565

Closed
CPerezz opened this issue Aug 30, 2021 · 1 comment
Closed

Migrate toAllocatedScalar in public API instead of Variable #565

CPerezz opened this issue Aug 30, 2021 · 1 comment
Assignees
@CPerezz
Labels
area:architecture Issues related to general architectural improvements to enhance performance and/or maintainabilty area:constraint_system Related to the Constraint Sysyem API or functionality status:invalid covers obsolete tasks, nonsensical issues, stuff that don't make sense (anymore) team:Core Low Level Core Development Team (Rust) type:feature implementing a new feature

Comments

@CPerezz
Copy link
Contributor

CPerezz commented Aug 30, 2021

No description provided.

@CPerezz CPerezz added area:constraint_system Related to the Constraint Sysyem API or functionality area:architecture Issues related to general architectural improvements to enhance performance and/or maintainabilty type:feature implementing a new feature team:Core Low Level Core Development Team (Rust) labels Aug 30, 2021
@CPerezz CPerezz self-assigned this Aug 30, 2021
CPerezz added a commit that referenced this issue Sep 3, 2021
@CPerezz
Update docs referencing the usage of AllocatedScalar
73a7307 
Resolves: #565
@CPerezz CPerezz mentioned this issue Sep 3, 2021
Merged
@CPerezz CPerezz mentioned this issue Sep 15, 2021
Closed
vlopes11 added a commit that referenced this issue Sep 30, 2021
@vlopes11
Refactor TurboComposer for API consistency
e6577fc 
The current`TurboComposer` API constaints a lot of legacy functions with
inconsistent signatures.

For the addition gate, we have `big_add`, `big_add_gate`, `add`,
`add_gate` with different signatures that internally perform the same
operation.

This commit aims to create an uniform API for the composer.

Resolves #565 , #583 , #584 , #587 , #588
@vlopes11 vlopes11 mentioned this issue Sep 30, 2021
Merged
vlopes11 added a commit that referenced this issue Sep 30, 2021
@vlopes11
Refactor TurboComposer for API consistency
3b04db7 
The current`TurboComposer` API constaints a lot of legacy functions with
inconsistent signatures.

For the addition gate, we have `big_add`, `big_add_gate`, `add`,
`add_gate` with different signatures that internally perform the same
operation.

This commit aims to create an uniform API for the composer.

Resolves #565 , #583 , #584 , #587 , #588
vlopes11 added a commit that referenced this issue Sep 30, 2021
@vlopes11
Refactor TurboComposer for API consistency
0cb7ae9 
The current`TurboComposer` API constaints a lot of legacy functions with
inconsistent signatures.

For the addition gate, we have `big_add`, `big_add_gate`, `add`,
`add_gate` with different signatures that internally perform the same
operation.

This commit aims to create an uniform API for the composer.

Resolves #565 , #583 , #584 , #587 , #588
vlopes11 added a commit that referenced this issue Sep 30, 2021
@vlopes11
Refactor TurboComposer for API consistency
774f3e2 
The current`TurboComposer` API constaints a lot of legacy functions with
inconsistent signatures.

For the addition gate, we have `big_add`, `big_add_gate`, `add`,
`add_gate` with different signatures that internally perform the same
operation.

This commit aims to create an uniform API for the composer.

Resolves #565 , #583 , #584 , #587 , #588
vlopes11 added a commit that referenced this issue Sep 30, 2021
@vlopes11
Refactor TurboComposer for API consistency
d4a3129 
The current`TurboComposer` API constaints a lot of legacy functions with
inconsistent signatures.

For the addition gate, we have `big_add`, `big_add_gate`, `add`,
`add_gate` with different signatures that internally perform the same
operation.

This commit aims to create an uniform API for the composer.

Resolves #565 , #583 , #584 , #587 , #588
vlopes11 added a commit that referenced this issue Sep 30, 2021
@vlopes11
Refactor TurboComposer for API consistency
b6ebd11 
The current`TurboComposer` API constaints a lot of legacy functions with
inconsistent signatures.

For the addition gate, we have `big_add`, `big_add_gate`, `add`,
`add_gate` with different signatures that internally perform the same
operation.

This commit aims to create an uniform API for the composer.

Resolves #565 , #583 , #584 , #587 , #588
vlopes11 added a commit that referenced this issue Sep 30, 2021
@vlopes11
Refactor TurboComposer for API consistency
507ebde 
The current`TurboComposer` API constaints a lot of legacy functions with
inconsistent signatures.

For the addition gate, we have `big_add`, `big_add_gate`, `add`,
`add_gate` with different signatures that internally perform the same
operation.

This commit aims to create an uniform API for the composer.

Resolves #565 , #583 , #584 , #587 , #588
vlopes11 added a commit that referenced this issue Sep 30, 2021
@vlopes11
Refactor TurboComposer for API consistency
cc9c448 
The current`TurboComposer` API constaints a lot of legacy functions with
inconsistent signatures.

For the addition gate, we have `big_add`, `big_add_gate`, `add`,
`add_gate` with different signatures that internally perform the same
operation.

This commit aims to create an uniform API for the composer.

Resolves #565 , #583 , #584 , #587 , #588
vlopes11 added a commit that referenced this issue Oct 1, 2021
@vlopes11
Refactor TurboComposer for API consistency
181c83c 
The current`TurboComposer` API constaints a lot of legacy functions with
inconsistent signatures.

For the addition gate, we have `big_add`, `big_add_gate`, `add`,
`add_gate` with different signatures that internally perform the same
operation.

This commit aims to create an uniform API for the composer.

Resolves #565 , #583 , #584 , #587 , #588
@ZER0 ZER0 added the status:invalid covers obsolete tasks, nonsensical issues, stuff that don't make sense (anymore) label Oct 6, 2021
@ZER0
Copy link
Contributor

ZER0 commented Oct 6, 2021

Not applicable anymore.

@ZER0 ZER0 closed this as completed Oct 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CPerezz CPerezz

Labels
area:architecture Issues related to general architectural improvements to enhance performance and/or maintainabilty area:constraint_system Related to the Constraint Sysyem API or functionality status:invalid covers obsolete tasks, nonsensical issues, stuff that don't make sense (anymore) team:Core Low Level Core Development Team (Rust) type:feature implementing a new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ZER0 @CPerezz