|
Ran
|
Jobs
1
|
Files
132
|
Run time
1min
|
Badge
README BADGES
|
push
github
Merge rust-bitcoin/rust-bitcoin#4800: Refactor how we call private macros <a class=hub.com/rust-bitcoin/rust-bitcoin/commit/2e28fddb21402fd393d71ca73249a598c64c5b35">2e28fddb2<a href="https://github.com/rust-bitcoin/rust-bitcoin/commit/d0ec281ce672c918c41952f9359631592bd332d5"> Use single level of path for internal macros (Tobin C. Harding) <a class="double-link" href="https://github.com/rust-bitcoin/rust-bitcoin/commit/8654c1d4c63d967d6598121ed9e7544fe2a1eb71">8654c1d4c</a> Use full path for internal consensus macros (Tobin C. Harding) Pull request description: How, when, and why we use macros has evolved over time. We are kind of only begrudgingly using them. And we are trying to not call them across crate boundaries. Clean up how we call private macros to use a single level of path so the calls are terse but explicit. ACKs for top commit: apoelstra: ACK 2e28fddb21402fd393d71ca73249a598c64c5b35; successfully ran local tests Tree-SHA512: a446260702d867c212a5921418e71da6fa4
21544 of 25817 relevant lines covered (83.45%)
15119.2 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 16836112683.1 | 132 |
83.45 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|