rust-bitcoin / rust-bitcoin/rust-miniscript
What are strategies to handle the error return of `max_weigh_to_satisfy` ?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 426
- Forks
- 200
- Avg merge
- 7d 17h
- Merged PRs (30d)
- 8
Description
Maybe upstream could add a field to the
Paramsstructure which would refuse to parse un-satiable descriptors. Could you file an issue in rust-miniscript asking for strategies to handle the error return of max_weight_to_satisfy?
Alternately you can just use
unwrap_or(usize::MAX)or something silly.
Originally posted by @apoelstra in https://github.com/bitcoindevkit/bdk/pull/1448#discussion_r1638247558
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue mentions max_weight_to_satisfy and the Params structure, but names no files, tests, or specific change. Start by locating that function and Params definition, then clarify an agreed strategy for handling unsatisfiable descriptors; the issue provides no concrete completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100