Richard Musiol 9e2a4f4dff syscall: remove support for O_NONBLOCK and O_SYNC on js/wasm ... This commit removes O_NONBLOCK on js/wasm. O_SYNC can't be removed, because it is referenced by the os package, so instead its use returns an error. On Windows, the options O_NONBLOCK and O_SYNC are not available when opening a file with Node.js. This caused the initialization of the syscall package to panic. The simplest solution is to not support these two options on js/wasm at all. Code written for js/wasm is supposed to be portable, so platform-specific options should not be used. Fixes #26524. Change-Id: I366aa3cdcfa59dfa9dc513368259f363ca090f00 Reviewed-on: https://go-review.googlesource.com/126600 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>		2018-07-31 17:03:39 +00:00
..
go_js_wasm_exec
wasm_exec.html	misc/wasm: make wasm_exec.js more flexible	2018-05-18 18:16:50 +00:00
wasm_exec.js	syscall: remove support for O_NONBLOCK and O_SYNC on js/wasm	2018-07-31 17:03:39 +00:00