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

Arity and multiple SBO #50

Open
jwaterloo opened this issue Feb 1, 2018 · 0 comments
Open

Arity and multiple SBO #50

jwaterloo opened this issue Feb 1, 2018 · 0 comments

Comments

@jwaterloo
Copy link

jwaterloo commented Feb 1, 2018

I don't know if any of this has merit. You know the whole storage versus execution trade off.
Is there compile time metadata on the arity or number of methods in the vtable?
If users were given a way to tag types as immutable then the following template constuctor pattern may be worth exploring. If the immutable object type is smaller or equal in size of its pointer then store a copy of the object instead. Also it may be possible to store a object of size 2 * pointer size - 1 byte if the number of virtual methods are less than 256 which will practically always be the case. In any case, the 2 pointer storage type should always be the same type. This logic, or at least part of it, being performed in the concept map instead of the poly.

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