• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

rust-bitcoin / rust-bitcoin / 11107515991 / 1
83%
master: 83%

Build:
DEFAULT BRANCH: master
Ran 30 Sep 2024 01:50PM UTC
Files 99
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

30 Sep 2024 01:49PM UTC coverage: 82.525% (-0.09%) from 82.619%
11107515991.1

push

github

apoelstra
Merge rust-bitcoin/rust-bitcoin#3358: Add Xpriv::to_xpub and improve related method names

<a class=hub.com/rust-bitcoin/rust-bitcoin/commit/<a class="double-link" href="https://git"><a class=hub.com/rust-bitcoin/rust-bitcoin/commit/e215a39dba173cdc616ab63b16a3eb8e02ac18ee">e215a39db<a href="https://github.com/rust-bitcoin/rust-bitcoin/commit/0b8c45ff8ed41ec4f27e947f08200ae9cd7c21b5"> Improve documentation of Xpub::from_xpriv (Jiri Jakes)
<a class="double-link" href="https://github.com/rust-bitcoin/rust-bitcoin/commit/0dcba9838250bb285d6cf096cb742bd1f31b309a">0dcba9838</a><a href="https://github.com/rust-bitcoin/rust-bitcoin/commit/0b8c45ff8ed41ec4f27e947f08200ae9cd7c21b5"> Add Xpriv::to_xpub (Jiri Jakes)
</a><a class="double-link" href="https://github.com/rust-bitcoin/rust-bitcoin/commit/5a9341bfc5bbc9ebac730e7415e7d1c34d014947">5a9341bfc</a> Improve naming of methods on Xpub and Xpriv (Jiri Jakes)

Pull request description:

  Adds `Xpriv::to_xpub` and makes naming of methods related to extended and non-extended keys on `Xpub` and `Xpriv` consistent and easier to discover:

    - if method takes or returns extended key, its name uses `xpriv` or `xpub`
    - if method takes or returns non-extended key, its name uses `public_key` or `private_key`

  Previous naming of the methods was confusing and unclear and this PR deprecates them.

  Closes #3327.

  ### Notes for reviewers

    - `xpriv` and `xpub` could be without `x`, I opted for this version to remove any ambiguity
    - also considered `raw` or similar name (as suggested) for methods with non-extended keys, however `raw` is usually not used in this context and `to_public_key` vs. `to_x_only_public_key` did not look alright with any other name
    - if splitting this PR into two would be desirable, please let me know
    - is there a reason why `ckd_priv` is private and `ckd_pub` is public?

ACKs for top commit:
  apoelstra:
    ACK e215a39dba173cdc616ab63b16a3eb8e02ac18ee successfully ran local tests
  tcharding:
    ACK e215a39dba173cdc616ab63b16a3eb8e02ac18ee

Tree-SHA512: f76b22740e0bd5f169921a9d7340439ca42

18994 of 23016 relevant lines covered (82.53%)

18189.88 hits per line

Source Files on job 11107515991.1
  • Tree
  • List 0
  • Changed 12
  • Source Changed 2
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 11107515991
  • 0b8c45ff on github
  • Prev Job for on master (#11093198648.1)
  • Next Job for on master (#11110281725.1)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc