Skip to content

no need to reserve 0 for "void" type #663

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

Closed
lukewagner opened this issue Apr 20, 2016 · 1 comment
Closed

no need to reserve 0 for "void" type #663

lukewagner opened this issue Apr 20, 2016 · 1 comment
Milestone

Comments

@lukewagner
Copy link
Member

#640 removes, I believe, the only case in the binary encoding where 0 is used to mean "no type". When we "defragment" the opcode space, it'd be good to remove this hole too.

@lukewagner lukewagner added this to the MVP milestone Apr 20, 2016
@lukewagner
Copy link
Member Author

Actually, like 0 for unreachable, it could be nice to keep 0 as a sentinel "no type" going forward.

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

No branches or pull requests

2 participants