Lines Matching refs:a

31 # file as a warning against manual editing
36 # Whether to include a comment with the version of cbindgen used to generate the file
41 # default: doesn't emit a namespace
72 # Whether to make a C header C++ compatible.
73 # These will wrap generated functions into a `extern "C"` block, e.g.
104 # The desired length of a line to use when formatting lines
141 # When generating a C header, the kind of declaration style to use for structs
253 # as `#[repr(packed)]`. For instance, "__attribute__((packed))" would be a
255 # involve emitting the name of a macro which you define in a platform-specific
259 # be unsafe for C callers to use a incorrectly laid-out union.
263 # as `#[repr(align(n))]`. This string must be a function-like macro which takes
264 # a single argument (the requested alignment, `n`). For instance, a macro
266 # `__attribute__((aligned(n)))` would be a reasonable value if targeting
270 # could be unsafe for C callers to use a incorrectly-aligned union.
297 # would be a reasonable value if targeting gcc/clang. A more portable solution
298 # would involve emitting the name of a macro which you define in a
306 # For instance, `__attribute__((noreturn))` would be a reasonable value if
328 # technically possible values (that shouldn't have a purpose here):
357 # technically possible values (that shouldn't have a purpose here):
368 # would be a reasonable value if targeting gcc/clang. A more portable solution
369 # would involve emitting the name of a macro which you define in a
375 # Whether a Rust type with associated consts should emit those consts inside the
383 # Whether to derive a simple constructor that takes a value for every field.
432 # technically possible values (that shouldn't have a purpose for the variants):
478 # would be a reasonable value if targeting gcc/clang. A more portable solution
479 # would involve emitting the name of a macro which you define in a
483 # with fields, as it will be emitted as a struct. `[struct]must_use` will apply there.
528 # Whether a generated constant can be a static const in C++ mode. I have no
534 # Whether a generated constant can be constexpr in C++ mode.
577 # Whether to use a new temporary target directory when running `rustc -Zunpretty=expanded`.
591 # parsing to expand any macros. Note that if a crate is named here, it
622 # `&mut T` and `NonNull<T>` all require a valid pointer value.