Allow blocklisting anonymous enums #3067
Conversation
jschwe
force-pushed
the
jschwender/blocklist_anon_enums
branch
from
05c2885 to
1d01b94
Compare
jschwe
force-pushed
the
jschwender/blocklist_anon_enums
branch
from
b87010a to
3b5da54
Compare
| { | ||
| debug!("Blocklisting anonymous enum."); | ||
| return; | ||
| } |
There was a problem hiding this comment.
Shouldn't this only block the enum if all variants, and not any are blocklisted? If not, can we document this behavior and why is it useful? thanks.
There was a problem hiding this comment.
The behavior of using any variant matches for anonymous enums is not new, and already works when allowlisting anonymous enums, so there is a (probably small) risk that changing the way matching works could break users who are relying on the current behavior for allowlisting.
There was a problem hiding this comment.
But you can individually hide variants (via annotations or callbacks), right...
I'd expect allowlisting to work with any and blocklisting to work with all, if that makes sense... But let me know if you disagree, maybe my expectation is flawed somehow?
Currently, there is no way to blocklist anonymous enums, which is inconvenient if you want to avoid
_bindgen_tyXXtypes appearing in the public API.Note: I'm not 100% sure if this is the best place to apply the blocklisting, but I couldn't find a more appropriate place.