Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

General audit of range length/remaining definitions and usage #10

Open
pineapplemachine opened this issue Dec 5, 2016 · 1 comment
Open

General audit of range length/remaining definitions and usage #10

pineapplemachine opened this issue Dec 5, 2016 · 1 comment
Labels
bug

Comments

@pineapplemachine
Copy link
Owner

pineapplemachine commented Dec 5, 2016 •
edited
Loading

Not a comprehensive list of issues:

Many ranges still lack a remaining property even where one should be valid.

The length property of heaps (which are also ranges) would be better described as remaining for a range.

The asarray implementations should refer to remaining rather than length when determining how many elements to expect.
@pineapplemachine
Copy link
Owner Author

This has currently been accomplished for most - but not all - packages in mach.range as part of a general cleanup and documentation effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pineapplemachine