SHLW $7, DX, (BX)                       // 660fa41307
	SHLW $7, R11, (BX)                      // 66440fa41b07
	SHLW $7, DX, (R11)                      // 66410fa41307
	SHLW $7, R11, (R11)                     // 66450fa41b07
	SHLW $7, DX, DX                         // 660fa4d207
	SHLW $7, R11, DX                        // 66440fa4da07
	SHLW $7, DX, R11                        // 66410fa4d307

			r:            strings.NewReader("abcdefghijklmnopqrstuvwxyz"),
			n:            27,
			want:         26,
			wantErr:      io.EOF,
			wantBuffered: 0,
		},
		// Any error from filling shouldn't show up until we
		// get past the valid bytes. Here we return 5 valid bytes at the same time
		// as an error, but test that we don't see the error from Discard.
		{
			name: "fill error, discard less",

</p>

<p>
For instance, some architectures provide a "fused multiply and add" (FMA) instruction
that computes <code>x*y + z</code> without rounding the intermediate result <code>x*y</code>.
These examples show when a Go implementation can use that instruction:
</p>

<pre>
// FMA allowed for computing r, because x*y is not explicitly rounded:
r  = x*y + z
r  = z;   r += x*y
t  = x*y; r = t + z

</p>

<p>
For instance, some architectures provide a "fused multiply and add" (FMA) instruction
that computes <code>x*y + z</code> without rounding the intermediate result <code>x*y</code>.
These examples show when a Go implementation can use that instruction:
</p>

<pre>
// FMA allowed for computing r, because x*y is not explicitly rounded:
r  = x*y + z
r  = z;   r += x*y
t  = x*y; r = t + z

pkg syscall (windows-386), const SW_MINIMIZE = 6
pkg syscall (windows-386), const SW_NORMAL = 1
pkg syscall (windows-386), const SW_RESTORE = 9
pkg syscall (windows-386), const SW_SHOW = 5
pkg syscall (windows-386), const SW_SHOWDEFAULT = 10
pkg syscall (windows-386), const SW_SHOWMAXIMIZED = 3
pkg syscall (windows-386), const SW_SHOWMINIMIZED = 2

	// Output:
	// 3
	// 5
}

func ExampleCut() {
	show := func(s, sep string) {
		before, after, found := bytes.Cut([]byte(s), []byte(sep))
		fmt.Printf("Cut(%q, %q) = %q, %q, %v\n", s, sep, before, after, found)
	}
	show("Gopher", "Go")
	show("Gopher", "ph")
	show("Gopher", "er")
	show("Gopher", "Badger")
	// Output:
	// Cut("Gopher", "Go") = "", "pher", true

      description: Breaking the Go 1 compatibility guarantee is a large cost and requires a large benefit.
      placeholder: |
       Yes or No

       If yes, 
        1. Show example code before and after the change.

    validations:
      required: true

  - type: textarea
    id: orthogonality
    attributes:

plain period and slash.
Within an assembler source file, the symbols above are written as
<code>fmt·Printf</code> and <code>math∕rand·Int</code>.
The assembly listings generated by the compilers when using the <code>-S</code> flag
show the period and slash directly instead of the Unicode replacements
required by the assemblers.
</p>

<p>
Most hand-written assembly files do not include the full package path

pkg syscall (windows-386), const SW_MINIMIZE ideal-int
pkg syscall (windows-386), const SW_NORMAL ideal-int
pkg syscall (windows-386), const SW_RESTORE ideal-int
pkg syscall (windows-386), const SW_SHOW ideal-int
pkg syscall (windows-386), const SW_SHOWDEFAULT ideal-int
pkg syscall (windows-386), const SW_SHOWMAXIMIZED ideal-int
pkg syscall (windows-386), const SW_SHOWMINIMIZED ideal-int

if [ "$GOARCH" == "arm64" ]; then
	SDK=iphoneos
	PLATFORM=ios
	CLANGARCH="arm64"
else
	SDK=iphonesimulator
	PLATFORM=ios-simulator
	CLANGARCH="x86_64"
fi

SDK_PATH=`xcrun --sdk $SDK --show-sdk-path`
export IPHONEOS_DEPLOYMENT_TARGET=5.1
# cmd/cgo doesn't support llvm-gcc-4.2, so we have to use clang.
CLANG=`xcrun --sdk $SDK --find clang`