]> git.bitcoin.ninja Git - ldk-java/commit
Be more conservative about holding a ref to a cloned object
authorMatt Corallo <git@bluematt.me>
Sat, 3 Aug 2024 02:37:12 +0000 (02:37 +0000)
committerMatt Corallo <git@bluematt.me>
Tue, 3 Sep 2024 14:10:11 +0000 (14:10 +0000)
commit29a9573986a462b45368ad49a93d1362e86cac4a
treecc34a15f1172d948879353c4c26d32261f9a1747
parenta596b453016d23f8f8acec1b83f691ac82eebbcb
Be more conservative about holding a ref to a cloned object

If we clone an object before passing to/from native code, we
generally don't need to hold a reference to that object in the
struct that owns the method.

The one exception we include here is if the object being passed is
either a trait or holds a reference to a trait. Its not clear if
this is required but it seems like a potential sharp edge.
bindingstypes.py
gen_type_mapping.py
genbindings.py