b := NewReaderSize(strings.NewReader("hello world"), BufSize)
	// Does it recognize itself?
	b1 := NewReaderSize(b, BufSize)
	if b1 != b {
		t.Error("NewReaderSize did not detect underlying Reader")
	}
	// Does it wrap if existing buffer is too small?
	b2 := NewReaderSize(b, 2*BufSize)
	if b2 == b {
		t.Error("NewReaderSize did not enlarge buffer")
	}
}

func TestNewWriterSizeIdempotent(t *testing.T) {

pkg syscall (freebsd-riscv64), const IFT_AFLANE8025 = 60 #53466
pkg syscall (freebsd-riscv64), const IFT_AFLANE8025 ideal-int #53466
pkg syscall (freebsd-riscv64), const IFT_ARAP = 88 #53466
pkg syscall (freebsd-riscv64), const IFT_ARAP ideal-int #53466
pkg syscall (freebsd-riscv64), const IFT_ARCNET = 35 #53466
pkg syscall (freebsd-riscv64), const IFT_ARCNET ideal-int #53466

the <a href="#Numeric_types">unsigned integer</a>'s type.
Loosely speaking, these unsigned integer operations
discard high bits upon overflow, and programs may rely on "wrap around".
</p>
<p>
For signed integers, the operations <code>+</code>,
<code>-</code>, <code>*</code>, <code>/</code>, and <code>&lt;&lt;</code> may legally

*/
package gmp

/*
#cgo LDFLAGS: -lgmp
#include <gmp.h>
#include <stdlib.h>

// gmp 5.0.0+ changed the type of the 3rd argument to mp_bitcnt_t,
// so, to support older versions, we wrap these two functions.
void _mpz_mul_2exp(mpz_ptr a, mpz_ptr b, unsigned long n) {
	mpz_mul_2exp(a, b, n);
}
void _mpz_div_2exp(mpz_ptr a, mpz_ptr b, unsigned long n) {
	mpz_div_2exp(a, b, n);
}
*/
import "C"

pkg syscall (netbsd-arm64-cgo), const IFT_AFLANE8025 = 60
pkg syscall (netbsd-arm64-cgo), const IFT_AFLANE8025 ideal-int
pkg syscall (netbsd-arm64-cgo), const IFT_ARAP = 88
pkg syscall (netbsd-arm64-cgo), const IFT_ARAP ideal-int
pkg syscall (netbsd-arm64-cgo), const IFT_ARCNET = 35
pkg syscall (netbsd-arm64-cgo), const IFT_ARCNET ideal-int
pkg syscall (netbsd-arm64-cgo), const IFT_ARCNETPLUS = 36

	// to _cgoCheckPointer, as done in checkIndex and checkAddr.
	//
	// When the function argument is a conversion to unsafe.Pointer,
	// we unwrap the conversion before checking the pointer,
	// and then wrap again when calling C.f. This lets us check
	// the real type of the pointer in some cases. See issue #25941.
	//
	// When the call to C.f is deferred, we use an additional function

pkg syscall (freebsd-arm64), const IFT_AFLANE8025 = 60
pkg syscall (freebsd-arm64), const IFT_AFLANE8025 ideal-int
pkg syscall (freebsd-arm64), const IFT_ARAP = 88
pkg syscall (freebsd-arm64), const IFT_ARAP ideal-int
pkg syscall (freebsd-arm64), const IFT_ARCNET = 35
pkg syscall (freebsd-arm64), const IFT_ARCNET ideal-int
pkg syscall (freebsd-arm64), const IFT_ARCNETPLUS = 36

pkg syscall (freebsd-386), const IFT_ADSL ideal-int
pkg syscall (freebsd-386), const IFT_AFLANE8023 ideal-int
pkg syscall (freebsd-386), const IFT_AFLANE8025 ideal-int
pkg syscall (freebsd-386), const IFT_ARAP ideal-int
pkg syscall (freebsd-386), const IFT_ARCNET ideal-int
pkg syscall (freebsd-386), const IFT_ARCNETPLUS ideal-int
pkg syscall (freebsd-386), const IFT_ASYNC ideal-int

computed modulo 2<sup><i>n</i></sup>, where <i>n</i> is the bit width of
the unsigned integer's type.
Loosely speaking, these unsigned integer operations
discard high bits upon overflow, and programs may rely on "wrap around".
</p>

<p>
For signed integers, the operations <code>+</code>,
<code>-</code>, <code>*</code>, <code>/</code>, and <code>&lt;&lt;</code> may legally

pkg syscall (freebsd-386), const IFT_ADSL = 94
pkg syscall (freebsd-386), const IFT_AFLANE8023 = 59
pkg syscall (freebsd-386), const IFT_AFLANE8025 = 60
pkg syscall (freebsd-386), const IFT_ARAP = 88
pkg syscall (freebsd-386), const IFT_ARCNET = 35
pkg syscall (freebsd-386), const IFT_ARCNETPLUS = 36
pkg syscall (freebsd-386), const IFT_ASYNC = 84
pkg syscall (freebsd-386), const IFT_ATM = 37