We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the VM now storing the types alongside the data in the stack, we should now be able to make custom functions with vague data types.
Values would still have distinct types in the VM, it would just mean that the VM would decide how to use them depending on their types.
We could always optimise by having more specific opcodes if we know for a fact a given value will be a distinct type.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
With the VM now storing the types alongside the data in the stack, we should now be able to make custom functions with vague data types.
Values would still have distinct types in the VM, it would just mean that the VM would decide how to use them depending on their types.
We could always optimise by having more specific opcodes if we know for a fact a given value will be a distinct type.
The text was updated successfully, but these errors were encountered: