[Java] Update auto-generated Java bindings for 0.0.116
[ldk-java] / src / main / java / org / ldk / structs / BroadcasterInterface.java
index ca3e82a7324eebb5ddfe071c54ddb13e58ad2c05..62679935a959c7b6da60189116c8e1d8a0d6b07a 100644 (file)
@@ -1,19 +1,89 @@
 package org.ldk.structs;
 
 import org.ldk.impl.bindings;
-
 import org.ldk.enums.*;
+import org.ldk.util.*;
+import java.util.Arrays;
+import java.lang.ref.Reference;
+import javax.annotation.Nullable;
 
+/**
+ * An interface to send a transaction to the Bitcoin network.
+ */
+@SuppressWarnings("unchecked") // We correctly assign various generic arrays
 public class BroadcasterInterface extends CommonBase {
-       BroadcasterInterface(Object _dummy, long ptr) { super(ptr); }
-       public BroadcasterInterface(bindings.LDKBroadcasterInterface arg) {
+       final bindings.LDKBroadcasterInterface bindings_instance;
+       BroadcasterInterface(Object _dummy, long ptr) { super(ptr); bindings_instance = null; }
+       private BroadcasterInterface(bindings.LDKBroadcasterInterface arg) {
                super(bindings.LDKBroadcasterInterface_new(arg));
                this.ptrs_to.add(arg);
+               this.bindings_instance = arg;
        }
        @Override @SuppressWarnings("deprecation")
        protected void finalize() throws Throwable {
-               bindings.BroadcasterInterface_free(ptr); super.finalize();
+               if (ptr != 0) { bindings.BroadcasterInterface_free(ptr); } super.finalize();
+       }
+       /**
+        * Destroys the object, freeing associated resources. After this call, any access
+        * to this object may result in a SEGFAULT or worse.
+        *
+        * You should generally NEVER call this method. You should let the garbage collector
+        * do this for you when it finalizes objects. However, it may be useful for types
+        * which represent locks and should be closed immediately to avoid holding locks
+        * until the GC runs.
+        */
+       public void destroy() {
+               if (ptr != 0) { bindings.BroadcasterInterface_free(ptr); }
+               ptr = 0;
+       }
+       public static interface BroadcasterInterfaceInterface {
+               /**
+                * Sends a list of transactions out to (hopefully) be mined.
+                * This only needs to handle the actual broadcasting of transactions, LDK will automatically
+                * rebroadcast transactions that haven't made it into a block.
+                * 
+                * In some cases LDK may attempt to broadcast a transaction which double-spends another
+                * and this isn't a bug and can be safely ignored.
+                * 
+                * If more than one transaction is given, these transactions should be considered to be a
+                * package and broadcast together. Some of the transactions may or may not depend on each other,
+                * be sure to manage both cases correctly.
+                * 
+                * Bitcoin transaction packages are defined in BIP 331 and here:
+                * https://github.com/bitcoin/bitcoin/blob/master/doc/policy/packages.md
+                */
+               void broadcast_transactions(byte[][] txs);
+       }
+       private static class LDKBroadcasterInterfaceHolder { BroadcasterInterface held; }
+       public static BroadcasterInterface new_impl(BroadcasterInterfaceInterface arg) {
+               final LDKBroadcasterInterfaceHolder impl_holder = new LDKBroadcasterInterfaceHolder();
+               impl_holder.held = new BroadcasterInterface(new bindings.LDKBroadcasterInterface() {
+                       @Override public void broadcast_transactions(byte[][] txs) {
+                               arg.broadcast_transactions(txs);
+                               Reference.reachabilityFence(arg);
+                       }
+               });
+               return impl_holder.held;
+       }
+       /**
+        * Sends a list of transactions out to (hopefully) be mined.
+        * This only needs to handle the actual broadcasting of transactions, LDK will automatically
+        * rebroadcast transactions that haven't made it into a block.
+        * 
+        * In some cases LDK may attempt to broadcast a transaction which double-spends another
+        * and this isn't a bug and can be safely ignored.
+        * 
+        * If more than one transaction is given, these transactions should be considered to be a
+        * package and broadcast together. Some of the transactions may or may not depend on each other,
+        * be sure to manage both cases correctly.
+        * 
+        * Bitcoin transaction packages are defined in BIP 331 and here:
+        * https://github.com/bitcoin/bitcoin/blob/master/doc/policy/packages.md
+        */
+       public void broadcast_transactions(byte[][] txs) {
+               bindings.BroadcasterInterface_broadcast_transactions(this.ptr, txs);
+               Reference.reachabilityFence(this);
+               Reference.reachabilityFence(txs);
        }
 
-       // Skipped BroadcasterInterface_broadcast_transaction
 }