Merge rust-bitcoin/rust-bitcoin#4665: Use relative import paths rather than absolute

c0345f8b8f Use relative import paths rather than absolute (Martin Habovstiak)

Pull request description:

  When doing large refactorings such as moving entire modules around referring to items defined in a parent module by mentioning `crate` is umbersome since the paths change and make the move confusing. It also obscures the fact that some concepts are related.
  
  This changes a few paths to relative so that the refactoring in the future will be easier.


ACKs for top commit:
  apoelstra:
    ACK c0345f8b8f617e5cf98bccb7500f2389511b1865; successfully ran local tests; lgtm
  tcharding:
    ACK c0345f8b8f


Tree-SHA512: 3c6e774c81ccdaa5b27b06f25e80385dd0972232a3267cdabb671c86ba86feaa2672185815430ad8efa1cf3888e05c897f5c43d8750d6a071bd970570d4574cb
This commit is contained in:
Andrew Poelstra 2025-07-03 15:46:33 +00:00
commit 9b4daa4192
No known key found for this signature in database
GPG Key ID: C588D63CE41B97C1
1 changed files with 1 additions and 2 deletions

View File

@ -62,11 +62,10 @@
use units::{BlockHeight, BlockHeightInterval};
use crate::network::Network;
use super::{Network, TestnetVersion};
#[cfg(doc)]
use crate::pow::CompactTarget;
use crate::pow::Target;
use crate::TestnetVersion;
/// Parameters that influence chain consensus.
#[non_exhaustive]