Add relevant no-export tags to functions returning builders 2023-10-various-followups
authorMatt Corallo <git@bluematt.me>
Mon, 23 Oct 2023 16:49:49 +0000 (16:49 +0000)
committerMatt Corallo <git@bluematt.me>
Mon, 23 Oct 2023 16:50:42 +0000 (16:50 +0000)
Because we can't map move semantics in most languages, we also
can't map our current builders. Thus, we have to mark them
no-export.

lightning/src/ln/channelmanager.rs

index e75b1a9273e4e3ef27bc66076ebcb92a7037d41d..2bf60cdc7971454d2afb30f8c6aef9eed9508d4a 100644 (file)
@@ -7331,6 +7331,8 @@ where
        /// Requires a direct connection to the introduction node in the responding [`InvoiceRequest`]'s
        /// reply path.
        ///
+       /// This is not exported to bindings users as builder patterns don't map outside of move semantics.
+       ///
        /// [`Offer`]: crate::offers::offer::Offer
        /// [`InvoiceRequest`]: crate::offers::invoice_request::InvoiceRequest
        pub fn create_offer_builder(
@@ -7384,6 +7386,8 @@ where
        /// Errors if a duplicate `payment_id` is provided given the caveats in the aforementioned link
        /// or if `amount_msats` is invalid.
        ///
+       /// This is not exported to bindings users as builder patterns don't map outside of move semantics.
+       ///
        /// [`Refund`]: crate::offers::refund::Refund
        /// [`Bolt12Invoice`]: crate::offers::invoice::Bolt12Invoice
        /// [`Bolt12Invoice::payment_paths`]: crate::offers::invoice::Bolt12Invoice::payment_paths