[Issue 8155] Deprecate std.range.lockstep

2016-10-16 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=8155 Andrei Alexandrescu changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 8155] Deprecate std.range.lockstep

2015-08-22 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=8155 Jack Stouffer changed: What|Removed |Added CC||j...@jackstouffer.com Depends on|

[Issue 8155] Deprecate std.range.lockstep

2013-07-04 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #17 from Joseph Rushton Wakeling 2013-07-04 03:10:53 PDT --- (In reply to comment #16) > If not already present I suggest you to open an enhancement request that asks > for your improvement of zip, and then we'll make this issue de

[Issue 8155] Deprecate std.range.lockstep

2013-06-29 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #16 from bearophile_h...@eml.cc 2013-06-29 03:16:46 PDT --- (In reply to comment #14) > I think deprecating lockstep in favour of zip is a no-no unless > one can do a systematic replace, 's/lockstep/zip/' and have the new code Just

[Issue 8155] Deprecate std.range.lockstep

2013-06-29 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #15 from Joseph Rushton Wakeling 2013-06-29 02:50:34 PDT --- (In reply to comment #14) > Glancing through the code, it looks like an issue of design difference > rather than a bug per se. The docs note that std.range.zip "offers m

[Issue 8155] Deprecate std.range.lockstep

2013-06-29 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #14 from Joseph Rushton Wakeling 2013-06-29 02:48:35 PDT --- (In reply to comment #13) > I see, for that I sometimes use a pattern like this: Very cool! :-) Nevertheless, I think deprecating lockstep in favour of zip is a no-no u

[Issue 8155] Deprecate std.range.lockstep

2013-06-28 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #13 from bearophile_h...@eml.cc 2013-06-28 17:18:28 PDT --- (In reply to comment #12) > In my real application, the value of x was determined by some rather complex > calculations for which i was a parameter, so copy doesn't work ei

[Issue 8155] Deprecate std.range.lockstep

2013-06-28 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #12 from Joseph Rushton Wakeling 2013-06-28 15:51:51 PDT --- (In reply to comment #11) > Such cases are better solved using the copy() algorithm. I accept the point, but I still think that the code given shouldn't fail with zip.

[Issue 8155] Deprecate std.range.lockstep

2013-06-28 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #11 from bearophile_h...@eml.cc 2013-06-28 13:57:42 PDT --- (In reply to comment #10) > Thanks for the useful hint :-) In fact in the general case where I discovered > this issue, the use case was more, > > foreach(i, ref x; l

[Issue 8155] Deprecate std.range.lockstep

2013-06-28 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #10 from Joseph Rushton Wakeling 2013-06-28 13:21:31 PDT --- (In reply to comment #9) > Let me add a note. For your specific use case it's better to use enumerate(), > from Issue 5550 : > > auto arr1 = new double[10]; > fo

[Issue 8155] Deprecate std.range.lockstep

2013-06-28 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #9 from bearophile_h...@eml.cc 2013-06-28 09:46:37 PDT --- (In reply to comment #8) > auto arr1 = new double[10]; > foreach(i, ref x; zip(iota(10), arr1)) > { > x = i; > } > writeln(arr1); > > auto a

[Issue 8155] Deprecate std.range.lockstep

2013-06-28 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 Joseph Rushton Wakeling changed: What|Removed |Added CC||joseph.wakel...@webdrake.ne

[Issue 8155] Deprecate std.range.lockstep

2012-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #7 from bearophile_h...@eml.cc 2012-06-05 16:36:14 PDT --- (In reply to comment #6) > You might introduce a new template tomorrow, and then remove it a month later, > so why should I even bother coding against such a library? Is Pho

[Issue 8155] Deprecate std.range.lockstep

2012-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #6 from Andrej Mitrovic 2012-06-05 15:18:38 PDT --- (In reply to comment #4) > (In reply to comment #3) > > Yes let's break code > > You can't assume Phobos will not change. You might introduce a new template tomorrow, and then

[Issue 8155] Deprecate std.range.lockstep

2012-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #5 from bearophile_h...@eml.cc 2012-06-05 15:04:06 PDT --- (In reply to comment #3) > Yes let's break code and make new code more verbose, great idea. Your answers have made those arguments of mine stronger, so thank you for your us

[Issue 8155] Deprecate std.range.lockstep

2012-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #4 from bearophile_h...@eml.cc 2012-06-05 15:01:26 PDT --- (In reply to comment #3) > Yes let's break code You can't assume Phobos will not change. Some parts of Phobos were designed very quickly, and not at their best. We need dep

[Issue 8155] Deprecate std.range.lockstep

2012-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #3 from Andrej Mitrovic 2012-06-05 14:15:51 PDT --- Yes let's break code and make new code more verbose, great idea. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mai

[Issue 8155] Deprecate std.range.lockstep

2012-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 --- Comment #2 from bearophile_h...@eml.cc 2012-06-05 13:45:11 PDT --- (In reply to comment #1) > Sorry, but I *do* use the index variable: I didn't said that index variable is never useful and never used. I have said its need is rare, in my ex

[Issue 8155] Deprecate std.range.lockstep

2012-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8155 Andrej Mitrovic changed: What|Removed |Added CC||andrej.mitrov...@gmail.com --- Comme