8 Jan
2015
8 Jan
'15
1:19 a.m.
"Edward Z. Yang" <ezyang@mit.edu> writes:
I propose to backwards incompatibly change the behavior of removeDirectoryRecursive to not follow symlinks. We could optionally add a replacement function under a new name which does follow symlinks.
+1 for changing it immediately, -1 for any deprecation period, -1 for adding the old one under another name Motivation: even if documented, the behaviour is severe bug with security implications. I don't think anyone in the right mind would expect such a function to follow symlinks.