-
Notifications
You must be signed in to change notification settings - Fork 13
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
Adds initial draft for iterators topic #90
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: JC van Winkel <[email protected]> Co-authored-by: Bogusław Cyganek <[email protected]> Co-authored-by: Jari Ronkainen <[email protected]>
|
||
Main Writing iterators | ||
|
||
Advanced --- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about "endowing iterators with execution policies" under advanced?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not mind at all this being added, but I would change the wording because I doubt "endow" is a common enough verb for every non-native speaker. I do not have a better replacement on the top of my head, maybe extend
, since it's more used in programming circles? It could be a bit too overloaded though and the sentence would become a bit clunky.
* Difference between value/reference semantics based for loops | ||
* Explain connection to for-each | ||
* Basic iterator nomenclature and functionality | ||
* begin/end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Explain that begin/end are methods for the container class, but advance/dereference are methods for the iterator class, which is a ?subclass? of the container class.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: JC van Winkel [email protected]
Co-authored-by: Bogusław Cyganek [email protected]
Co-authored-by: Jari Ronkainen [email protected]