When using -i, consistently creates a sed file at current working directory on Windows10

[Minh-Tâm TRAN]

Hello,

In a company working with Windows OS, I am trying to get used to tools from
the unix world.

I think I found a bug using sed on version 4.2.1 on Windows 10 that I got
from http://gnuwin32.sourceforge.net/packages/sed.htm


Given a file named "foo", containing the string "bar",
The following command:

sed -i "s/bar/baz" foo

correctly transforms "bar" to "baz" in the file "foo".

However, I always have a sed[something] file that is created in the
directory from which I run the scrip.
For example: sedObrnzt

I have tried the following commands, which give the same outcome:
sed -i"" "s/bar/baz" foo
sed --in-place "s/bar/baz" foo
sed --in-place= "s/bar/baz" foo
sed --in-place="" "s/bar/baz" foo

Is it reasonable to ask for a fix ?

I observed that sed version 4.0.7 does not have this issue, but it would
still be nice to fix it in version 4.2.1 I think.

Best regards,
-- 
Minh-Tâm TRAN
Computing Science & Applied maths N7 Engineer