Struct autocxx_parser::IncludeCppConfig [−][src]
pub struct IncludeCppConfig {
pub inclusions: Vec<String>,
pub unsafe_policy: UnsafePolicy,
pub parse_only: bool,
pub exclude_impls: bool,
// some fields omitted
}Fields
inclusions: Vec<String>unsafe_policy: UnsafePolicyparse_only: boolexclude_impls: boolImplementations
impl IncludeCppConfig[src]
impl IncludeCppConfig[src]pub fn get_pod_requests(&self) -> &[String][src]
pub fn get_mod_name(&self) -> Ident[src]
pub fn exclude_utilities(&self) -> bool[src]
pub fn exclude_utilities(&self) -> bool[src]Whether to avoid generating the standard helpful utility functions which we normally include in every mod.
pub fn must_generate_list(&self) -> Box<dyn Iterator<Item = String>>[src]
pub fn must_generate_list(&self) -> Box<dyn Iterator<Item = String>>[src]Items which the user has explicitly asked us to generate; we should raise an error if we weren’t able to do so.
pub fn bindgen_allowlist(&self) -> Option<Box<dyn Iterator<Item = String>>>[src]
pub fn bindgen_allowlist(&self) -> Option<Box<dyn Iterator<Item = String>>>[src]The allowlist of items to be passed into bindgen, if any.
pub fn is_on_allowlist(&self, cpp_name: &str) -> bool[src]
pub fn is_on_allowlist(&self, cpp_name: &str) -> bool[src]Whether this type is on the allowlist specified by the user.
A note on the allowlist handling in general. It’s used in two places:
- As directives to bindgen
- After bindgen has generated code, to filter the APIs which we pass to cxx. This second pass may seem redundant. But sometimes bindgen generates unnecessary stuff.
pub fn is_on_blocklist(&self, cpp_name: &str) -> bool[src]
pub fn get_blocklist(&self) -> impl Iterator<Item = &String>[src]
pub fn get_makestring_name(&self) -> String[src]
Trait Implementations
impl Debug for IncludeCppConfig[src]
impl Debug for IncludeCppConfig[src]impl Hash for IncludeCppConfig[src]
impl Hash for IncludeCppConfig[src]impl Parse for IncludeCppConfig[src]
impl Parse for IncludeCppConfig[src]