|
Ran
|
Jobs
1
|
Files
113
|
Run time
1min
|
Badge
README BADGES
|
push
github
Merge rust-bitcoin/rust-bitcoin#3561: bitcoin: Re-format crate level re-exports <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/6555143478dbd2306d0506a29b7d83433e7b33f5">655514347 bitcoin: Re-format crate level re-exports (Tobin C. Harding) Pull request description: Is there any advantage trying to lay out the re-exports to give users an idea of the crate structure? We have the explicit aim that users who depend on `bitcoin` do not ever need to reach directly into `primitives` (or `units`) however it is kind of nice to know where things come from, saves jumping to multiple files looking for them (for those of us that jump to files manually). I do not know how all the re-exports interact with other folks IDEs, I personally open files manually and just remember where stuff is. ACKs for top commit: jamillambert: ACK 6555143478dbd2306d0506a29b7d83433e7b33f5 apoelstra: ACK 6555143478dbd2306d0506a29b7d83433e7b33f5; successfully ran local tests; If Jamil and Tobin are happy then I am happy Tree-SHA512: 15fc9bec60b37e8b41e1a42d4c39e6efa06
19695 of 23880 relevant lines covered (82.47%)
18190.67 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 11669495867.1 | 0 |
82.47 |
GitHub Action Run |