@@ -1419,10 +1419,8 @@ options! {
14191419 /// Note that they will usually not work. However you can use `-fkeep-inline-functions`
14201420 /// or `-fno-inline-functions` if you are responsible of compiling the library to make
14211421 /// them callable.
1422- #[ cfg_attr(
1423- feature = "experimental" ,
1424- doc = "\n Check the [`Builder::wrap_static_fns`] method for an alternative."
1425- ) ]
1422+ ///
1423+ /// Check the [`Builder::wrap_static_fns`] method for an alternative.
14261424 pub fn generate_inline_functions( mut self , doit: bool ) -> Self {
14271425 self . options. generate_inline_functions = doit;
14281426 self
@@ -2021,7 +2019,6 @@ options! {
20212019 /// Whether to generate wrappers for `static` functions.
20222020 wrap_static_fns: bool {
20232021 methods: {
2024- #[ cfg( feature = "experimental" ) ]
20252022 /// Set whether to generate wrappers for `static`` functions.
20262023 ///
20272024 /// Passing `true` to this method will generate a C source file with non-`static`
@@ -2040,7 +2037,6 @@ options! {
20402037 /// The suffix to be added to the function wrappers for `static` functions.
20412038 wrap_static_fns_suffix: Option <String > {
20422039 methods: {
2043- #[ cfg( feature = "experimental" ) ]
20442040 /// Set the suffix added to the wrappers for `static` functions.
20452041 ///
20462042 /// This option only comes into effect if `true` is passed to the
@@ -2057,7 +2053,6 @@ options! {
20572053 /// The path of the file where the wrappers for `static` functions will be emitted.
20582054 wrap_static_fns_path: Option <PathBuf > {
20592055 methods: {
2060- #[ cfg( feature = "experimental" ) ]
20612056 /// Set the path for the source code file that would be created if any wrapper
20622057 /// functions must be generated due to the presence of `static` functions.
20632058 ///
0 commit comments