xrange__core's Introduction

`@xrange/core`

The very core of `xrange`, provided as a separate package

_{Created with create-package-typescript}

Differences from `xrange`:

only numeric implementation with two or three numeric arguments: xrange(start, stop, step?);
no proper support of decimal numbers, only integers;
no custom errors, such as "argument is required" or "argument must infinite";
no intelligent boundary swapping, — e.g., xrange(10, 1) will not iterate;
only Node.JS is supported (for now at least);

xrange__core's People

Contributors

Watchers

xrange__core's Issues

Publish dependency updates from #1

Make protocol-compliant implementation manually

This requires implementing a wrapper around core (@xrange/core) or reimplementing core to plain (although iterator-protocol-compliant) object, rather than a generator.

Originally posted by @parzhitsky in parzh/xrange#59 (comment)

Remove parameters from (future) `.return(…)` method

Protocol-compliant implementation assumes .return(…) method having a parameter, that's basically passed through as the return value of the method's call. Since xrange is a number iterator, it is designed to return "nothing" (i.e., undefined) after the iterated range is finished (the current NaN is temporary as per parzh/xrange#50), which means that the returned value of .return(…) is always an implicit undefined, and it doesn't depend on any inputs.