on the <code>TEXT</code> instruction.
The pointer information can also be omitted if the
function contains no call instructions.
Otherwise, the local stack frame must not contain pointers,
and the assembly must confirm this fact by executing the
pseudo-instruction <code>NO_LOCAL_POINTERS</code>.
Because stack resizing is implemented by moving the stack,
the stack pointer may change during any function call:

error message, but this package reserves the right to not force a fault on
freed memory. That means a valid implementation of this package is to just
allocate all memory the way the runtime normally would, and in fact, it
reserves the right to occasionally do so for some Go values.
*/
package arena

import (
	"internal/reflectlite"
	"unsafe"
)

// Arena represents a collection of Go values allocated and freed together.

embedded field in a struct <code>x</code> is called <i>promoted</i> if
<code>x.f</code> is a legal <a href="#Selectors">selector</a> that denotes
that field or method <code>f</code>.
</p>

<p>
Promoted fields act like ordinary fields
of a struct except that they cannot be used as field names in
<a href="#Composite_literals">composite literals</a> of the struct.
</p>

<p>

pkg syscall (openbsd-386), const TCP_MAXWIN = 65535
pkg syscall (openbsd-386), const TCP_MAX_SACK = 3
pkg syscall (openbsd-386), const TCP_MAX_WINSHIFT = 14
pkg syscall (openbsd-386), const TCP_MD5SIG = 4
pkg syscall (openbsd-386), const TCP_MSS = 512
pkg syscall (openbsd-386), const TCP_NSTATES = 11
pkg syscall (openbsd-386), const TCP_SACK_ENABLE = 8
pkg syscall (openbsd-386), const TCSAFLUSH = 2

If either of these two types contains type parameters, type inference looks for the
type arguments to substitute the type parameters with such that the assignability
relationship is satisfied.
Similarly, type inference uses the fact that a type argument must
<a href="#Satisfying_a_type_constraint">satisfy</a> the constraint of its respective
type parameter.
</p>

<p>

pkg syscall (openbsd-386), const TCP_MAX_SACK ideal-int
pkg syscall (openbsd-386), const TCP_MAX_WINSHIFT ideal-int
pkg syscall (openbsd-386), const TCP_MD5SIG ideal-int
pkg syscall (openbsd-386), const TCP_MSS ideal-int
pkg syscall (openbsd-386), const TCP_NSTATES ideal-int
pkg syscall (openbsd-386), const TCP_SACK_ENABLE ideal-int
pkg syscall (openbsd-386), const TCSAFLUSH ideal-int

	go func() { a = "hello" }()
	print(a)
}
</pre>

<p>
the assignment to <code>a</code> is not followed by
any synchronization event, so it is not guaranteed to be
observed by any other goroutine.
In fact, an aggressive compiler might delete the entire <code>go</code> statement.
</p>

<p>
If the effects of a goroutine must be observed by another goroutine,
use a synchronization mechanism such as a lock or channel

func discard(r io.Reader, n int64) error {
	// If possible, Seek to the last byte before the end of the data section.
	// Do this because Seek is often lazy about reporting errors; this will mask
	// the fact that the stream may be truncated. We can rely on the
	// io.CopyN done shortly afterwards to trigger any IO errors.
	var seekSkipped int64 // Number of bytes skipped via Seek
	if sr, ok := r.(io.Seeker); ok && n > 1 {