skiptools / skiptools/skip.dev
Document ClosedRange limitations
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 32
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
On Slack, @marcprux wrote:
Unfortunately Kotlin doesn't distinguish between open and closed ranges (see https://github.com/skiptools/skip-lib/issues/30 and https://github.com/skiptools/skip-lib/issues/28). So just using open ranges is probably the best workaround. In theory, we could potentially work around this by performing our own conversion from closed ranges into open ranges (for integer values).
But the Transpilation Reference just says:
✓ Range operators
I don't think that's a correct representation of Skip Lite's support for ranges.
https://skip.dev/docs/bridging/ makes no mention at all of ranges.
Even https://github.com/skiptools/skip-lib/blob/main/README.md makes no mention of ClosedRange. It lists an orange dot 🟠 for Range, and lists a few of its most important methods as functional.
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 with the Transpilation Reference at https://skip.dev/docs/swiftsupport/, the bridging page at https://skip.dev/docs/bridging/, and the skip-lib README linked in the issue. Document that ClosedRange support is limited, explain the open-range workaround, and ensure the listed Range support matches the actual behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, swift
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100