rust-bitcoin / rust-bitcoin/rust-bitcoin
Tracking Issue: API Regressions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 88
Description
A place for downstream users to register that we changed the API in a way that makes their code worse. Please post liberally, if we made your code worse we care - in each case we can decide if we were in the wrong and should backport the original API (if possible) or if we stand by the new API.
We appreciate all feedback, negative and positive (negative is more valuable than positive - so be brave).
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
Start by reviewing the downstream API regression reports and discussion in this tracking issue. Identify the affected public API for each report, then determine whether the original API can be restored or the new API should stand; the work is complete when each report has a recorded decision and follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend-api-design
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100