-
Notifications
You must be signed in to change notification settings - Fork 98
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.
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
API Iterators/generators consistency #75
Comments
Honestly, I don't longer remember the reasoning, and will have to go over it. |
Is it possible (though it's horrible) to support both simultaneously somehow (and mark one way as deprecated)? P.S. as you know, I have my fair share of scripts to update accordingly, I am not taking it lightly. |
In case you guys want this, I needed something pretty similar at one point and I wrote some pretty hacky-looking code that combines an iterator with a list. It adds a
(edited to add comments) |
Hello,
Almost in every class there are many iterator/generator properties and methods.
Sometimes it's a method (e.g.
CodeBlock.succs()
is a generator of succeeding blocks) and sometimes it's a property (e.g.CodeBlock.prev
). I failed to understand when a property is used and when a method is used which makes the library less usable. It's quite confusing and forces the user to check the documentation more frequently than necessary (which reduces usability and makes the library 'surprising' in a bad way).If there is any logic behind these decisions, can you share and document them?
If not, can you align it please?
Thanks
The text was updated successfully, but these errors were encountered: