Document ClosedRange limitations #12
Description
On Slack, @marcprux wrote:
Unfortunately Kotlin doesn't distinguish between open and closed ranges (see skiptools/skip-lib#30 and skiptools/skip-lib#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.