Kill method on windows calls the parent kill method. Whereas if you see an equivalent Terminate call, it calls terminate on a windows process handle.
To Reproduce
// paste example code reproducing the bug you are reporting
I was doing a comparison with python and I found that kill in python works only on UNIX systems. Hence, I believe the same issue may be applicable here as well.
Expected behavior
[A clear and concise description of what you expected to happen.]
Either inform users that kill is not supported on windows or perform a sigterm if that works.
Environment (please complete the following information):
[ ] Windows: [paste the result of ver]
[ ] Linux: [paste contents of /etc/os-release and the result of uname -a]
[ ] Mac OS: [paste the result of sw_vers and uname -a
[ ] FreeBSD: [paste the result of freebsd-version -k -r -u and uname -a]
[ ] OpenBSD: [paste the result of uname -a]
Additional context
[Cross-compiling? Paste the command you are using to cross-compile and the result of the corresponding go env]
Describe the bug [A clear and concise description of what the bug is.]
Kill method on windows calls the parent kill method. Whereas if you see an equivalent Terminate call, it calls terminate on a windows process handle.
To Reproduce
I was doing a comparison with python and I found that kill in python works only on UNIX systems. Hence, I believe the same issue may be applicable here as well.
Expected behavior [A clear and concise description of what you expected to happen.]
Either inform users that kill is not supported on windows or perform a sigterm if that works.
Environment (please complete the following information):
ver
]/etc/os-release
and the result ofuname -a
]sw_vers
anduname -a
freebsd-version -k -r -u
anduname -a
]uname -a
]Additional context [Cross-compiling? Paste the command you are using to cross-compile and the result of the corresponding
go env
]