Surrounding the calls in a try-catch every time we want to ignore unlink failures seems excessive... Maybe instead there can be two methods 'tryRemove' and 'remove'? tryRemove would do the same logic as remove now but return true/false based on whether remove succeeds or not. remove would use tryRemove and if false, throws.

What do you think?

Yep that makes sense. But is that very common to remove files but not actually care if they are really deleted?

No, but I would assume in most cases we wouldn't want a failed remove to result in an exception that causes the request to fail. So there may be custom error handling, and using a try-catch every time for something as simple as file deletion seems verbose to me.

Updated the code to optionally log a warning instead of throwing an exception. I've used a method parameter instead of defining a new method to avoid creating too many similar methods.