-
Notifications
You must be signed in to change notification settings - Fork 0
Redefine XRange as IterableIterator<number> instead of a generator #498
Copy link
Copy link
Open
Labels
Change: major[Issue / PR] describes a breaking change of any kind[Issue / PR] describes a breaking change of any kindDomain: main[Issue / PR] describes change in the functionality, its optimization[Issue / PR] describes change in the functionality, its optimizationPriority: medium[Issue / PR] should be addressed without delay[Issue / PR] should be addressed without delayType: improvement[Issue / PR] addresses lack of a functionality or an open possibility of enhancement[Issue / PR] addresses lack of a functionality or an open possibility of enhancement
Metadata
Metadata
Assignees
Labels
Change: major[Issue / PR] describes a breaking change of any kind[Issue / PR] describes a breaking change of any kindDomain: main[Issue / PR] describes change in the functionality, its optimization[Issue / PR] describes change in the functionality, its optimizationPriority: medium[Issue / PR] should be addressed without delay[Issue / PR] should be addressed without delayType: improvement[Issue / PR] addresses lack of a functionality or an open possibility of enhancement[Issue / PR] addresses lack of a functionality or an open possibility of enhancement
Change definition of
XRangetype toIterableIterator<number>both inxrangeand@xrange/corepackages:https://github.com/parzh/xrange/blob/develop/src/typings/xrange.ts#L7(already deprecated)XRange(define it exactly once in@xrange/core)