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

Consider using different uint types (e.g., u8,u16 or u32) instead of usize #3

Open
aarkue opened this issue Aug 23, 2024 · 0 comments

Comments

@aarkue
Copy link
Owner

aarkue commented Aug 23, 2024

Currently, event/object indices as well as variables and their bindings and so on are all represented as usize.
However, for most if not all realistic use cases a smaller representation would already suffice and would allow for constructing a large number of bindings.

It would be interesting to investigate if this could make sense using the following steps:

  • Abstract the underlying datatype as a generic type parameter (for event/object indices and for variables seperately.
  • Handle these generics in all execution functions, check how to best handle them in typescript type conversions etc.
  • Evaluate if the memory usage is observably different for simple and complex queries/constraints
  • Evaluate if the execution is observably different for simple and complex queries/constraints
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

No branches or pull requests

1 participant