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

Rigorously bound the Clarity Value sizes in VM #911

Closed
kantai opened this issue Feb 6, 2019 · 3 comments

Comments

@kantai
Copy link
Member

commented Feb 6, 2019

We should enforce a maximum byte limit for types.

@kantai kantai self-assigned this Feb 6, 2019
@kantai kantai added the design label Feb 6, 2019
@jcnelson

This comment has been minimized.

Copy link
Member

commented Feb 6, 2019

Does this refer to the size of atoms, or lists, or both?

@kantai

This comment has been minimized.

Copy link
Member Author

commented Feb 6, 2019

Both -- so we'd have a maximum size for a value in the system -- neither lists nor atoms (e.g., very large tuples) could exceed the size.

@kantai

This comment has been minimized.

Copy link
Member Author

commented Feb 6, 2019

One important thing to note is that this has to be a maximum size enforced at the language level -- we don't want it to be the case that changes in the interpreter's representation of values could change this.

@kantai kantai added the clarity label Jun 4, 2019
@kantai kantai changed the title Add a bound for Value types in VM Rigorously bound the Clarity Value sizes in VM Aug 15, 2019
@kantai kantai closed this Sep 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.