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.

Sign up for GitHub

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

Jump to bottom

DYNO_INTERFACE() customizable storage policy. #35

Open
lucas93 opened this issue Nov 7, 2017 · 1 comment
Open

DYNO_INTERFACE() customizable storage policy. #35

lucas93 opened this issue Nov 7, 2017 · 1 comment
Labels
feature

Comments

@lucas93
Copy link

lucas93 commented Nov 7, 2017

Hi Louis. Great work!
What is the default DYNO_INTERFACE() macro storage policy? You could consider a way to let the user specify the storage policy when using a new one / this macro.
@ldionne
Copy link
Owner

ldionne commented Nov 8, 2017

Thank you!

Currently, DYNO_INTERFACE ends up using a dyno::poly with the default storage policy, which is (currently) dyno::remote_storage, i.e. storage on the heap. I do plan to make it possible to customize the storage used with DYNO_INTERFACE. I will leave this issue open to track the progress of this.

@ldionne ldionne added the feature label Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ldionne @lucas93