feat: add intRange type

[Emiyaaaaa]

Fixes #669

[sindresorhus]

Thanks for contributing :)

[sindresorhus]

How does this compare to https://twitter.com/anuraghazru/status/1573328100246822917 and #669 (comment) ?

[sindresorhus]

I'm a little bit concerned about possible type complexity explosion here. Have you tested it with larger ranges?

Maybe it would make sense to add an overload to use the simpler way when "step" is not specified?

[sindresorhus]

// @lucasteles @tommy-mitchell

[Emiyaaaaa]

I'm a little bit concerned about possible type complexity explosion here. Have you tested it with larger ranges?

Maybe it would make sense to add an overload to use the simpler way when "step" is not specified?

You are right, with "step" is significantly slower than without "step". I found EqualOrMoreThan is very performance-impairing, but it is necessary for "step"

I should use overload and try to resolve performance question with Step.

ps: range limit is 0-999 in any implementation

[Emiyaaaaa]

How does this compare to https://twitter.com/anuraghazru/status/1573328100246822917 and #669 (comment) ?

these are the same principle: generate a Start to End tuple like type RangeArray<5, 10> = [5,6,7,8,9], and transform it to union.

anuraghazru and #669 way is generate a number tuple A of "0 - Start" and anonter number tuple B of "0 - End". then Exclude<B, A>

My why is generate a tuple of "0 - End", and use any other type when tuple index is small than Start, (e.x. type IntRangeArray<3, 5> = [never, never, never, 3, 4]), than transform tuple to union and exclude never, so ohter way created two tuple but my way just create one tuple and just need one loop.

anuraghazru's "float range" implementation way is transform IntRange result to string union, then add the decimals, finally transform it to number union

[Emiyaaaaa]

I'm a little bit concerned about possible type complexity explosion here. Have you tested it with larger ranges?
Maybe it would make sense to add an overload to use the simpler way when "step" is not specified?

You are right, with "step" is significantly slower than without "step". I found EqualOrMoreThan is very performance-impairing, but it is necessary for "step"

I should use overload and try to resolve performance question with Step.

ps: range limit is 0-999 in any implementation

@sindresorhus The latest commit used overload and improved performance when use Step, now can fast load IntRange<0, 999, 2> without loading in vscode

[sindresorhus]

Thanks :)