sstadick / sstadick/rust-lapper
merge_overlaps loses values
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 71
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
merge_overlaps seems to take the value from the first Interval that overlaps and the other value is lost. I'm not sure the best way to handle this? Maybe a user-provided merge function that lets you create a new value when merging two ranges?
Contributor guide
No contributing guide indexed for this repository
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 reading the merge_overlaps API and reproducing the reported behavior with overlapping intervals carrying different values. Clarify the intended value-merging semantics, then add coverage for the chosen behavior; done means overlapping values are handled without silently losing one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100