Skip to content

Conversation

@TheBlueMatt
Copy link
Collaborator

When building a slice with `slice::from_raw_parts`, we're required
to pass in a non-NULL pointer even if the length is 0. While we did
this in most cases, we weren't always careful about it. Here we fix
the issue by using a simple wrapper which passes a dummy pointer
instead.
Because we're always reading from a fixed-length buffer anyway, we
can always support it with our existing code.
There's no need for this assertion, the code should be the same
between named fields and tuple fields.
Both new `rust-bitcoin` types as well as support for `i32` and
cloning `Option_NoneZ`.
We'd always intended to do this, but never got around to it, so
might as well.
Sadly its not currently possible to map `lightning-liquidity` to
bindings as it requires additional (`Clone`) bounds on various
trait objects passed in to the top-level manager constructor.
Because we don't anticipate bindings users using it immediately, we
simply drop it here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant