On 6/25/20 11:27 AM, Pavel Rappo wrote:
I think that knowing that is superfluous in most cases. If we choose a bigger block (e.g. java.nio.file.Files#copy(java.nio.file.Path, java.nio.file.Path, java.nio.file.CopyOption...)) and capture the implicated files in a DocFileIOException, that could be more practical.
It would be better if a Lego block like Files#copy were more friendly and was specified to throw an exception from which you could obtain the Path that failed and the underlying cause.
-- Jon
