Why does the request()->all() method do an array_replace_recursive instead of a array_merge_recursive?

[jesseheidstra]

As the title says, why does request()->all() use the array_replace_recursive method instead of the array_merge_recursive?
Maybe there is a good reason im not thinking about but here is my use-case and why it is annoying.

Im using the Filepond plugin to do my file uploads. On the initial store there is no problem because they are all new files,
but when i want to edit my model i will load my initial files again through an url. If i add a new file and post it my files array would be this:

[ 0 => 'http://foo.test/media/1' (string of the existing file because we dont want to re-upload them), 1 => Illuminate\Http\UploadedFile{} (The new file we are trying to upload) ]

but this is not what i get when i do a request()->all(), what i get is:

[ 0 => Illuminate\Http\UploadedFile{} (The new file we are trying to upload) ]

and that is because of the array_replace_recursive in the request()->all() method.
The reason i want the full array is because i want to order my files aswell.
I know i can do this in other ways but im just curious why the request()->all() method does what i described above and if this is intended behaviour.

Thank you in advance :)

[jesseheidstra]

I see now that my use-case isnt even going to work the way PHP handles form data and files, sorry for the useless discussion.