oh please come on!
Don't you think use bigint may indicate a non everyday use case?
Neither bigint nor Math::BigInt mention this problem or even the range operator.
And maybe it's even possible to fix by overloading ".." in UNIVERSAL.¹
Cheers Rolf
UPDATE:
1) seems like overloading the range operator was never intended: Overloadable Operations
In reply to Re^4: c-style for loop versus list for loop, and bigint
by LanX
in thread c-style for loop versus list for loop, and bigint
by AR
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |