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

Consider Adding Scope Option Setter or Option Flags #16

Open
samuelkgutierrez opened this issue Mar 8, 2022 · 0 comments
Open

Consider Adding Scope Option Setter or Option Flags #16

samuelkgutierrez opened this issue Mar 8, 2022 · 0 comments
Assignees

Comments

@samuelkgutierrez
Copy link
Member

samuelkgutierrez commented Mar 8, 2022

Consider adding something like qv_scope_options(). This would allow for the setting of context-specific options before creation. A use-case I have in mind is setting an option that would allow for a standalone mode where starting a user-space daemon is handled automatically at startup. I'm sure there are other use-cases, but this one comes to mind.

A complication is that we would have to allocate a context and initialize its parameters and then be able to determine at qv_*_scope_get() time that the structure has already been allocated with options set. Maybe we can embed a magic value at the top of the structure to make this possible? Or we can add flags at creation time (this is probably the easiest/cleanest route).

@samuelkgutierrez samuelkgutierrez self-assigned this Mar 8, 2022
@samuelkgutierrez samuelkgutierrez changed the title Consider Adding Context Option Setter or Option Flags Consider Adding Scope Option Setter or Option Flags Jul 4, 2024
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