if (this.exited) {
				this._resolveExitPromise();
			}
		}

		_makeFuncWrapper(id) {
			const go = this;
			return function () {
				const event = { id: id, this: this, args: arguments };
				go._pendingEvent = event;
				go._resume();
				return event.result;
			};
		}
	}

<p>
the function calls and communication happen in the order
<code>f()</code>, <code>h()</code>, <code>i()</code>, <code>j()</code>,
<code>&lt;-c</code>, <code>g()</code>, and <code>k()</code>.
However, the order of those events compared to the evaluation
and indexing of <code>x</code> and the evaluation
of <code>y</code> is not specified.
</p>

<pre>
a := 1
f := func() int { a++; return a }

pkg syscall (linux-386), const PTRACE_DETACH = 17
pkg syscall (linux-386), const PTRACE_EVENT_CLONE = 3
pkg syscall (linux-386), const PTRACE_EVENT_EXEC = 4
pkg syscall (linux-386), const PTRACE_EVENT_EXIT = 6
pkg syscall (linux-386), const PTRACE_EVENT_FORK = 1
pkg syscall (linux-386), const PTRACE_EVENT_VFORK = 2
pkg syscall (linux-386), const PTRACE_EVENT_VFORK_DONE = 5
pkg syscall (linux-386), const PTRACE_GETEVENTMSG = 16897

<code>f()</code>, <code>h()</code> (if <code>z</code>
evaluates to false), <code>i()</code>, <code>j()</code>,
<code>&lt;-c</code>, <code>g()</code>, and <code>k()</code>.
However, the order of those events compared to the evaluation
and indexing of <code>x</code> and the evaluation
of <code>y</code> and <code>z</code> is not specified,
except as required lexically. For instance, <code>g</code>

pkg syscall (linux-arm-cgo), const PTRACE_EVENT_CLONE ideal-int
pkg syscall (linux-arm-cgo), const PTRACE_EVENT_EXEC ideal-int
pkg syscall (linux-arm-cgo), const PTRACE_EVENT_EXIT ideal-int
pkg syscall (linux-arm-cgo), const PTRACE_EVENT_FORK ideal-int
pkg syscall (linux-arm-cgo), const PTRACE_EVENT_VFORK ideal-int
pkg syscall (linux-arm-cgo), const PTRACE_EVENT_VFORK_DONE ideal-int

go.exit = process.exit;
WebAssembly.instantiate(fs.readFileSync(process.argv[2]), go.importObject).then((result) => {
	process.on("exit", (code) => { // Node.js exits if no event handler is pending
		if (code === 0 && !go.exited) {
			// deadlock, make Go print error and stack traces
			go._pendingEvent = { id: 0 };
			go._resume();
		}
	});
	return go.run(result.instance);

"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,

for a minimum of two years (four Go releases).
Some, such as `http2client` and `http2server`,
will be maintained much longer, even indefinitely.

When possible, each GODEBUG setting has an associated
[runtime/metrics](/pkg/runtime/metrics/) counter
named `/godebug/non-default-behavior/<name>:events`
that counts the number of times a particular program's
behavior has changed based on a non-default value
for that setting.

pkg syscall (linux-386), const PTRACE_EVENT_CLONE ideal-int
pkg syscall (linux-386), const PTRACE_EVENT_EXEC ideal-int
pkg syscall (linux-386), const PTRACE_EVENT_EXIT ideal-int
pkg syscall (linux-386), const PTRACE_EVENT_FORK ideal-int
pkg syscall (linux-386), const PTRACE_EVENT_VFORK ideal-int
pkg syscall (linux-386), const PTRACE_EVENT_VFORK_DONE ideal-int

pkg syscall (windows-386), const CTRL_CLOSE_EVENT = 2
pkg syscall (windows-386), const CTRL_CLOSE_EVENT ideal-int
pkg syscall (windows-386), const CTRL_LOGOFF_EVENT = 5
pkg syscall (windows-386), const CTRL_LOGOFF_EVENT ideal-int
pkg syscall (windows-386), const CTRL_SHUTDOWN_EVENT = 6
pkg syscall (windows-386), const CTRL_SHUTDOWN_EVENT ideal-int
pkg syscall (windows-amd64), const CTRL_CLOSE_EVENT = 2