1<!-- Thanks for filing a bindgen issue! We appreciate it :-) -->
2
3### Input C/C++ Header
4
5```C++
6// Insert your minimal C or C++ header here.
7//
8// It should *NOT* have any `#include`s! Not all systems have the same header
9// files, and therefore any `#include` harms reproducibility. Additionally,
10// the test case isn't minimal since the included file almost assuredly
11// contains things that aren't necessary to reproduce the bug, and makes
12// tracking it down much more difficult.
13//
14// Use the `--dump-preprocessed-input` flag or the
15// `bindgen::Builder::dump_preprocessed_input` method to make your test case
16// standalone and without `#include`s, and then use C-Reduce to minimize it:
17// https://github.com/rust-lang/rust-bindgen/blob/master/CONTRIBUTING.md#using-creduce-to-minimize-test-cases
18```
19
20### Bindgen Invocation
21
22<!-- Place either the `bindgen::Builder` or the command line flags used here. -->
23
24```Rust
25bindgen::Builder::default()
26    .header("input.h")
27    .generate()
28    .unwrap()
29```
30
31or
32
33```
34$ bindgen input.h --whatever --flags
35```
36
37### Actual Results
38
39```
40Insert panic message and backtrace (set the `RUST_BACKTRACE=1` env var) here.
41```
42
43and/or
44
45```rust
46// Insert the (incorrect/buggy) generated bindings here
47```
48
49and/or
50
51```
52Insert compilation errors generated when compiling the bindings with rustc here
53```
54
55### Expected Results
56
57<!--
58Replace this with a description of what you expected instead of the actual
59results. The more precise, the better! For example, if a struct in the generated
60bindings is missing a field that exists in the C/C++ struct, note that here.
61-->
62