4865d60258
These re-exports are hard to get right. We (I) recently made an attempt to make our stack of crates easier to navigate using the idea that exporting a type from the crate it is defined in adds some additional information without any loss of clarity. Note however that the module must be re-exported from the "highest" place possible because we at times add additional functionality as we move up the stack e.g., `bitcoin::merkle_tree` has logic in it that `primitives::merkle_tree` does not. In order to future proof the codebase default to always using the highest module up the stack even when that module adds no additional code e.g., re-export `blockdata::fee_rate` as opposed to `units::fee_rate` in the event that we later add logic to `bitcoin::blockdata::fee_rate`. This patch adds an additional re-export: `sequence` (previously missing). |
||
|---|---|---|
| .. | ||
| contrib | ||
| embedded | ||
| examples | ||
| src | ||
| tests | ||
| CHANGELOG.md | ||
| Cargo.toml | ||