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.

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

Dynamic lookups #413

Closed
ETatuzova opened this issue Jul 11, 2024 · 0 comments · Fixed by #414
Closed

Dynamic lookups #413

ETatuzova opened this issue Jul 11, 2024 · 0 comments · Fixed by #414
Assignees

Comments

@ETatuzova
Copy link
Contributor

ETatuzova commented Jul 11, 2024

Any component may reserve any dynamic lookup table from lookup_library by name.
This table will have its own id and won't take part in table packing procedures

Some component may define dynamic table by given name. This means that this component will assignments for this table, add lookup_table structure to constraint system, store lookup_table in the library, it may be retrieved by table name

Table with given name should be defined only once.
Other components may create lookup_constraints for this table. It may be done before table will be defined.

Related to NilFoundation/crypto3#283

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant