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

chore(AztecMacro): separate entrypoint calls and kernel FunctionData #6548

Closed
Tracked by #5077
Thunkar opened this issue May 21, 2024 · 0 comments · Fixed by #6557
Closed
Tracked by #5077

chore(AztecMacro): separate entrypoint calls and kernel FunctionData #6548

Thunkar opened this issue May 21, 2024 · 0 comments · Fixed by #6557
Assignees
@Thunkar

Comments

@Thunkar
Copy link
Contributor

Thunkar commented May 21, 2024

function_data.nr and its associated typings are used both by entrypoint calls and the kernel. After the inclusion of is_static the kernel circuits grew even though that property is not used there (we only check if the context is static, not the function itself).

The types must be separated and the kernel cleaned up.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Thunkar Thunkar

Labels
None yet
Projects
A3
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: clean up kernel types by removing is_static from function_data AztecProtocol/aztec-packages
1 participant
@Thunkar