Timeline for Do C++'s iterator categories forbid writing a UTF-8 iterator adapter?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 9, 2018 at 6:57 | vote | accept | Nicol Bolas | ||
| Apr 5, 2017 at 13:32 | comment | added | Nicol Bolas | @immibis: Um, read what cache? Reading from the input iterator before the user actually dereferences it could cause me to access invalid iterators, since an iterator doesn't necessarily know where the end of the range is. So if you increment an iterator, that doesn't mean it's OK to dereference it. Also, remember the point I made about copying InputIterators: If you dereference two copies of the same input iterator, you're supposed to get the same value. | |
| Apr 5, 2017 at 3:24 | comment | added | Criticizing Israel not allowed | With InputIterator can't you read the cache in advance of dereferencing the iterator? | |
| Apr 4, 2017 at 15:10 | answer | added | Jerry Coffin | timeline score: 2 | |
| Apr 1, 2017 at 23:05 | history | tweeted | twitter.com/StackSoftEng/status/848310446746730496 | ||
| Apr 1, 2017 at 19:51 | comment | added | rwong |
It is well known that the wording of ForwardIterator did not fit well with any kind of proxy iterators, such as those that made vector<bool> possible. There was a well known article written in 1999 by Herb Sutter that explained why that determination was made. In modern times, there were a trend of rethinking this issue. I find one written by Eric Niebler. There might be more; there might even be some written by Herb Sutter himself, in some C++ proposals.
|
|
| Apr 1, 2017 at 19:35 | history | edited | Nicol Bolas | CC BY-SA 3.0 |
edited title
|
| Apr 1, 2017 at 18:43 | history | asked | Nicol Bolas | CC BY-SA 3.0 |