https://issues.dlang.org/show_bug.cgi?id=12293
--- Comment #5 from monarchdo...@gmail.com --- (In reply to Andrej Mitrovic from comment #4) > (In reply to Kenji Hara from comment #3) > > (In reply to Andrej Mitrovic from comment #2) > > > No, I've changed the title. See the history here: > > > https://issues.dlang.org/show_activity.cgi?id=12293 > > > > If the reason comes from just your feeling, I cannot agree with the title. > > I wasn't the one to suggest it, it was monarchdodra. What !? > AndrejMitrovic commented 4 days ago > https://issues.dlang.org/show_bug.cgi?id=12293 > > Honestly I think forward doesn't belong in std.algorithm. > It should likely belong to std.functional or a similar place. > Hence why I had to add a "utility" category. I'd rather we > just move the template out of std.algorithm though. You suggested it. I just told you to go through with it. > Originally I made the > pull that added 'forward' to the cheat-sheet of the std.algorithm page. I > can recreate this pull again if desired. Sure. > > std.algorithm.forward is in the same category of std.algorithm.move and > > swap. > > Why they are in std.algorithm module? Because in C++03, std::swap was in > > <algorithm> header. So in D, swap, move, and forward are in std.algorithm. > > That sounds reasonable to me then. Unless monarchdodra objects I'll recreate > the cheat-sheet pull. Sounds reasonable to me too. Revert back to how it was? --