Asynchronous error handling on file operations

When you copy or move files, you often get the files conflict dialog to decide if to skip or to overwrite (all) files, or a warning dialog, when a file is write protected. This of course is nice, but:
Why not continue copying the non-conflicting files in the background, while the dialog is open?

The current scenario: Start to copy 4000 files. Have a nice coffee break with colleagues. Go back to your desk, see that file 1700 of 4000 is write protected and now waits for input, and so only 1699 files were copied. Decide if to skip or overwrite all, and wait for the remaining 2300 files to copy.

An ideal scenario: Start to copy 4000 files. Have a nice coffee break with colleagues. Go back to your desk, see that 3990 files were successfully copied, and just resolve the 10 files in conflict.

I don't think that it is very important, since this scenario doesnt happen very often (in most cases conflicts will happen at the beginning of a file operation), but if it would not be too much work to implement it, it would be a good idea though, I think.

It's already on the to-do list, but not trivial to implement so nobody knows when it'll happen at this stage.

It's definitely a great idea to continue copying / moving the files that can be copied / moved in the background. Any update to the roadmap when this will be available?

GPSoftware haven't announced anything but they rarely talk about future features/versions in case plans change or are delayed.