Use ranges when we can [RFQ]

[fulldecent]

This breaks API so we need to:

• Implement new API
• Reimplement old API utilizing new API
• Mark old API as deprecated

And then create a new issue:

• Remove deprecated API
• Bump major version

---

Changes

• Change zoomSamples* to a range (this change is cosmetic)
  • Remove zoomStartSamples
  • Remove zoomEndSamples
  • Add zoomSamples: CountableClosedRange<Int>
• Change highlightedSamples to a range (related: Using 3+ colors #42, Multiple colors of Progress Samples #43 ) (this change now allows highlighting from somewhere that does not start at zero)
  • Remove progressSamples
  • Add highlightedRange: CountableClosedRange<Int>?
  • Rename progressColor to highlightColor

---

Implementation notes

Ranges have a few nifty methods that we can use:

• func clamped(to: Range<Bound>)
• func contains(Bound)
• func overlaps(Range<Bound>)

[fulldecent]

Hopefully we can work on #80 before this.

[fulldecent]

Hello world. Please provide some feedback here.

[pixlwave]

This change certainly makes sense, good to see the progress of this project. #80 looks like a pretty mega change to implement first though.

[fulldecent]

@pixlwave Thanks for the feedback. We are making progress on #80, we now have a merge commit so more people can easily test it.

[fulldecent]

Version bump discussed in #97