On Sunday, 3 April 2016 at 03:28:48 UTC, jmh530 wrote:
On Saturday, 2 April 2016 at 22:54:09 UTC, Lass Safin wrote:
You're right in how it isn't obvious for non-techy people. I
do suppose it would be doable without breaking any old code
(unless for some arcane reason the code depends on static
assert(!__traits(allMember, std.file).canFind("move"))...), so
why not create a PR with "alias move = rename" inside?
If I were looking at the documentation with fresh eyes, I would
be just as confused as the OP's brother. It's not about being
non-techy. Someone had an issue with the documentation and
commenting on their inexperience won't improve the
documentation. The documentation has no examples. It doesn't
mention file paths at all. I.e., easy to get confused.
Moreover, posix systems have mv, which can move and rename. mv
is a crappy name, but at least if the function would have the
same semantics as mv, they could have named it move instead of
rename. Seems like a silly breaking change at this point, so
they should just improve the docs.
To be fair I've always thought that mv is a bad name because
moving really is just renaming, there are no two separate
operations. That said I too would have searched for "move" first
exactly because as misleading as the name can be it corresponds
to what the user wants to do.
