Skip to content

[0.0.106-bindings] Restrict ChannelInfo::as_directed_from visibility #1407

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

jkczyz
Copy link
Contributor

@jkczyz jkczyz commented Apr 3, 2022

Required changes for bindings generation. Same as #1400 but based on the right commit.

TheBlueMatt and others added 5 commits April 3, 2022 16:41
We don't really care about more than this in bindings - calling
into a custom `Score` is likely too slow to be practical anyway,
so this is also a performance improvement.

Works around rust-lang/rust#90448
...as the bindings generation does not currently have the ability
to map a reference to a `NodeId` inside a tuple.
.. as the current C bindings generator isn't capable of handling
type aliases in generics in type alias definition currently.
Apparently documentation only applies to the first feature-specific
definition, not both.
Bindings can't handle references in return types, so reduce the
visibility to pub(crate).
@TheBlueMatt TheBlueMatt merged commit 0357f6a into lightningdevkit:0.0.106-bindings Apr 3, 2022
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.

2 participants