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

Selector functions #19

Open
emesare opened this issue Nov 4, 2024 · 0 comments
Open

Selector functions #19

emesare opened this issue Nov 4, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@emesare
Copy link
Member

emesare commented Nov 4, 2024

When it comes time to add more static libs that might be more niche and less broad, one might want to forbid matching unless specific functions are found, these would be "selector" functions that enable the rest of the dataset to be matched on. The idea would be to add another optional entry to the Function table called "selector" which can be as simple as a boolean value, or in case we want to encode more assumptions like chained selectors (think: function matches because of function existing elsewhere) some table called "Selector".

@emesare emesare added the enhancement New feature or request label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant