[Issue 5036] Remove caching from ranges
https://issues.dlang.org/show_bug.cgi?id=5036 --- Comment #7 from github-bugzi...@puremagic.com --- Commits pushed to 2.067 at https://github.com/D-Programming-Language/phobos https://github.com/D-Programming-Language/phobos/commit/8bb453a983d97da27454d96875cd5c574a72241d Fix Issue 5036 - Remove caching from Sequence https://github.com/D-Programming-Language/phobos/commit/76504e6e2eaf28517a0385fcbbe2e22d1c06f710 Merge pull request #2834 from Poita/Issue5036 --
[Issue 5036] Remove caching from ranges
https://issues.dlang.org/show_bug.cgi?id=5036 --- Comment #6 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/phobos https://github.com/D-Programming-Language/phobos/commit/8bb453a983d97da27454d96875cd5c574a72241d Fix Issue 5036 - Remove caching from Sequence This appears to be the last caching range in Phobos. This is a potentially breaking change: we lose the ability to moveFront, and obviously there may be performance implications if the function is expensive and users are calling front more than once. I think this is still a worthwhile change since it is better to have a uniform policy of no caching on ranges rather than arbitrary selection of ranges that do caching. https://issues.dlang.org/show_bug.cgi?id=5036 https://github.com/D-Programming-Language/phobos/commit/76504e6e2eaf28517a0385fcbbe2e22d1c06f710 Merge pull request #2834 from Poita/Issue5036 Fix Issue 5036 - Remove caching from Sequence --
[Issue 5036] Remove caching from ranges
https://issues.dlang.org/show_bug.cgi?id=5036 github-bugzi...@puremagic.com changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --
[Issue 5036] Remove caching from ranges
https://issues.dlang.org/show_bug.cgi?id=5036 Peter Alexander changed: What|Removed |Added CC||peter.alexander...@gmail.co ||m Assignee|and...@erdani.com |peter.alexander...@gmail.co ||m --- Comment #5 from Peter Alexander --- https://github.com/D-Programming-Language/phobos/pull/2834 --
[Issue 5036] Remove caching from ranges
https://issues.dlang.org/show_bug.cgi?id=5036 Dmitry Olshansky changed: What|Removed |Added CC||dmitry.o...@gmail.com --- Comment #4 from Dmitry Olshansky --- Sequence still has cache, I'm not sure to what extent it's a problem. --
[Issue 5036] Remove caching from ranges
https://issues.dlang.org/show_bug.cgi?id=5036 hst...@quickfur.ath.cx changed: What|Removed |Added CC||hst...@quickfur.ath.cx --- Comment #3 from hst...@quickfur.ath.cx --- Does this problem still occur? Over the last little while, many ranges have been rewritten to not cache their elements by default (unless there was reason to do so). Are there any specific ranges that cache .front in a problematic way? If not, can we close this bug? --
[Issue 5036] Remove caching from ranges
http://d.puremagic.com/issues/show_bug.cgi?id=5036 --- Comment #2 from Tomasz Sowiński 2013-02-26 12:28:04 PST --- The argument was the least about consistency, I recall caching got in the way when the mapped to element was: - used <= 1 times - trivial to calculate (faster than read/write) - manually allocated (harder to anticipate destruction) Plus, front/back vs. opIndex poses problems of their own. Why the obligation to cache? -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 5036] Remove caching from ranges
http://d.puremagic.com/issues/show_bug.cgi?id=5036 --- Comment #1 from Andrei Alexandrescu 2013-02-26 08:56:37 PST --- Hm, I think things are fine as they are, though I agree with the consistency argument. Agree to close? -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 5036] Remove caching from ranges
http://d.puremagic.com/issues/show_bug.cgi?id=5036 Tomasz Sowiński changed: What|Removed |Added Status|NEW |ASSIGNED AssignedTo|nob...@puremagic.com|and...@metalanguage.com -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
