@@ -1419,10 +1419,8 @@ options! {
1419
1419
/// Note that they will usually not work. However you can use `-fkeep-inline-functions`
1420
1420
/// or `-fno-inline-functions` if you are responsible of compiling the library to make
1421
1421
/// 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.
1426
1424
pub fn generate_inline_functions( mut self , doit: bool ) -> Self {
1427
1425
self . options. generate_inline_functions = doit;
1428
1426
self
@@ -2021,7 +2019,6 @@ options! {
2021
2019
/// Whether to generate wrappers for `static` functions.
2022
2020
wrap_static_fns: bool {
2023
2021
methods: {
2024
- #[ cfg( feature = "experimental" ) ]
2025
2022
/// Set whether to generate wrappers for `static`` functions.
2026
2023
///
2027
2024
/// Passing `true` to this method will generate a C source file with non-`static`
@@ -2040,7 +2037,6 @@ options! {
2040
2037
/// The suffix to be added to the function wrappers for `static` functions.
2041
2038
wrap_static_fns_suffix: Option <String > {
2042
2039
methods: {
2043
- #[ cfg( feature = "experimental" ) ]
2044
2040
/// Set the suffix added to the wrappers for `static` functions.
2045
2041
///
2046
2042
/// This option only comes into effect if `true` is passed to the
@@ -2057,7 +2053,6 @@ options! {
2057
2053
/// The path of the file where the wrappers for `static` functions will be emitted.
2058
2054
wrap_static_fns_path: Option <PathBuf > {
2059
2055
methods: {
2060
- #[ cfg( feature = "experimental" ) ]
2061
2056
/// Set the path for the source code file that would be created if any wrapper
2062
2057
/// functions must be generated due to the presence of `static` functions.
2063
2058
///
0 commit comments