Emilio Cobos Álvarez
Emilio Cobos Álvarez
Err, I meant the `[defines]` section. So when you do something like: ``` [defines] "feature=platform-a" = "PLATFORM_A" "feature=platform-b" = "PLATFORM_B" "feature=platform-c" = "PLATFORM_C" ``` You'll get something like: ``` #if...
> I tested it, and it doesn't work exactly as I hoped. Is it possible tto generate `#if PLATFFORM_A == 1` instead? It is not impossible. > Relying on `defined()`...
@dzervas it may be you want `/// cbindgen:ignore` on the module that has all the bindings that you don't want exported?
Totally would take a patch for that to allow tweaking it. Should be straight-forward. `enumeration.rs` contains the hard-coded `Sentinel` string, which can be taken from the config instead.
It may make sense to make the internal AST part of the public API (then another library could use it to generate JSON / yaml / whatever...). I suspect this...
And also which part of the AST do we want to expose... the monomorphized one? The one with generics?
Is there any chance you can provide a test-case that reproduces the panic?
That should already work afaict.
Is the ABI of `[T; N]` exactly equivalent in all cases to `struct { T member[N]; };`? I don't _think_ so. I think this is one of those cases where...
Yes, I don't see how that's safer than just `pub type K = [u64; 2];`