Add ParseCallbacks::allow_or_block_item(). #3245
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nicopauss
force-pushed
the
intersec/add-parse-callbacks-methods
branch
from
430055d to
89385ad
Compare
ivmaykov
reviewed
Sep 5, 2025
nicopauss
force-pushed
the
intersec/add-parse-callbacks-methods
branch
from
89385ad to
0b570dc
Compare
nicopauss
changed the title
Like `allowlist_item` and `blocklist_item` options, add new methods to `ParseCallbacks`, `ParseCallbacks::allow_item()` and `ParseCallbacks::block_item()`, to be able to allow and block items from being generated. `allowlist_*` and `blocklist_*` options work with regexes and are inserted in a RegexSet. There are two issues with this approach: 1. In some cases, we want to have more flexibility than just using regexes. If we want to have dynamic conditions to allow or block items, using regexes can be limited. 2. RegexSet scales linearly with the number of elements inserted. This means that if we have a huge number of items that we want to allow or block, regexes and RegexSet are not necessarily the most appropriate data structures. Using a new method in `ParseCallbacks` solves these two issues. We can manually decide the appropriate rules and data structure to match the items. This method takes precedences over the `allowlist_*` options. If at least one of the parse callbacks returns `Block`, the generation of the bindings for the item is blocked. If all the parse callbacks that don't return `None` return `Allow`, the bindings for the item are generated. If all the parse callbacks return `None` (the default implementation), the `allowlist_*` options are used instead.
nicopauss
force-pushed
the
intersec/add-parse-callbacks-methods
branch
from
0b570dc to
f819034
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Like
allowlist_itemandblocklist_itemoptions, add new methods toParseCallbacks,ParseCallbacks::allow_item()andParseCallbacks::block_item(), to be able to allow and block items from being generated.allowlist_*andblocklist_*options work with regexes and are inserted in a RegexSet.There are two issues with this approach:
Using a new method in
ParseCallbackssolves these two issues.We can manually decide the appropriate rules and data structure to match the items.
This method takes precedences over the
allowlist_*options.If at least one of the parse callbacks returns
Block, the generation of the bindings for the item is blocked.If all the parse callbacks that don't return
NonereturnAllow, the bindings for the item are generated.If all the parse callbacks return
None(the default implementation), theallowlist_*options are used instead.