Emilio Cobos Álvarez
Emilio Cobos Álvarez
This should be possible and not too hard. We have per-item annotations, and very similar code to control whitelisting / blacklisting. I'd be happy to help writing / review a...
(Sorry for the lag btw! :/)
Well, in practice most people don't really use the u / U suffix, so we try to pick an appropriate size. In any case you can override this: https://docs.rs/bindgen/0.50.0/bindgen/callbacks/trait.ParseCallbacks.html#method.int_macro
That is fair. I'm not opposed to changing behavior here in theory. The macro evaluator (https://github.com/jethrogb/rust-cexpr) doesn't provide any information other than the final `i64` value, so fixing this requires...
It may be ok to do that, but I'm not 100% sure ergonomics are better... Specially since macros in pre-2018 edition (I think?) are subject to module ordering, so if...
Hmm, this is interesting, thanks for filing. Of the recently-landed commits on LLVM, https://github.com/llvm/llvm-project-staging/commit/72131423cc952ccbd6d8e021ff7c04fa22297fe3 looks the most suspect, but it needs to be double-checked / bisected to be sure. It'd...
This is an issue with file blocklisting (haven't dug if it's a bug or just a weird side effect of whatever's going on). If you diff the generated bindings, you'll...
It seems like the filename we're testing against is `./fmod_dsp_effects.h` rather than `fmod_dsp_effects.h`... This comes directly from `clang_getFileName`, it seems a bit unexpected
The difference between `__BindgenUnionField` or not depends on the blocklist behavior, because it depends on whether bindgen thinks it can safely derive `Copy` for those things. So that sounds expected...
> it segfaults which is neat. What's the stack for that? It might be that you're overflowing the stack. > yields the ItemId to the interface that we actually want...