Funny to think that the issue here is just a relative of the 'no-preserve-root' feature rm (now) has: it's easy to let the user use the same actions equally on

Funny to think that the issue here is just a relative of the 'no-preserve-root' feature rm (now) has: it's easy to let the user use the same actions equally on the branches of a hierarchy as you could the leaves, but should they? Pretty recently corporate changed something on my work laptop that resulted in a bunch of temporary files generated during the build getting redirected to OneDrive. I went in and nuked the temp files and shortly thereafter got a message from OD saying 'hey noticed you trashed a ton of files, did you mean to do that?' The developer side of me thought 'of course I did, duh' but I can imagine that's useful information for most users that made an innocent yet potentially costly mistake.