misc range

[timotheecour]

links

[timotheecour]

• changing a param from int to Natural (or some range) can cause subtle change in semantics as explained in os.sleep: change type to: milsecs: Natural nim-lang/Nim#17149 (comment)

[timotheecour]

• range as return type causes other problems too, refs:

in nim-lang/Nim@8ee0771#commitcomment-38239130 araq argued "return types must not be Natural" (this came up recently here: nim-lang/fusion#18 (comment)), and instead suggested using {.ensures: cond.} for that.

[juancarlospaco]

Can compiler generate a warning when return type is a range ?.

[timotheecour]

it wouldn't be hard, but this should wait until {.ensures: cond.} is implemented (and honored by checks:on), refs nim-lang/RFCs#270, after which we can probably replace range (a non-transparent abstraction) into nim-lang/RFCs#270 (comment) (maybe).