If you can point to an example that depends on the windows-specific error,
could you post it in the issue?
On Sun, Aug 4, 2019, 2:16 AM Reto wrote:
> On Wed, Jul 31, 2019 at 07:00:46PM -0700, Liam wrote:
> > In this issue, Microsoft suggested that Go on Windows switch to
> Unix-like
> > behavio
>They did:
>https://github.com/golang/go/issues/32088#issuecomment-502850674
No, that's not a member of the go team.
>TL;DR; setting it by default would move the things to a little bit more
>
>POSIXy, but
>possibly creating more hiddent deviations.
yeah but that wasn't my question was it?
--
2019. augusztus 4., vasárnap 11:15:58 UTC+2 időpontban Reto a következőt
írta:
>
> On Wed, Jul 31, 2019 at 07:00:46PM -0700, Liam wrote:
> > In this issue, Microsoft suggested that Go on Windows switch to
> Unix-like
> > behavior in Go 1.14:
> > https://github.com/golang/go/issues/32088
> >
On Wed, Jul 31, 2019 at 07:00:46PM -0700, Liam wrote:
> In this issue, Microsoft suggested that Go on Windows switch to Unix-like
> behavior in Go 1.14:
> https://github.com/golang/go/issues/32088
>
> I believe this will change early in pre-release 1.14.
May I inquire as to why you believe that?
Microsoft recommends changing syscall.Open() for GOOS=windows to fix this.
Pls reply if you know of existing apps that rely on it.
This code fails with a "sharing violation" on Windows. That behavior is
undocumented in package "os".
path := "rename-after-open"
fd, err := os.OpenFile(path, os.O_
