- Sort Score
- Result 10 results
- Languages All
Results 1 - 9 of 9 for sage (0.12 sec)
-
.github/ISSUE_TEMPLATE/01-pkgsite.yml
labels: ["pkgsite"] body: - type: markdown attributes: value: "Please answer these questions before submitting your issue. Thanks!" - type: input id: url attributes: label: "What is the URL of the page with the issue?" validations: required: true - type: input id: user-agent attributes: label: "What is your user agent?"
Others - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu Jan 04 23:31:17 GMT 2024 - 1.4K bytes - Viewed (0) -
doc/go1.17_spec.html
<pre> [...]Point{{1.5, -3.5}, {0, 0}} // same as [...]Point{Point{1.5, -3.5}, Point{0, 0}} [][]int{{1, 2, 3}, {4, 5}} // same as [][]int{[]int{1, 2, 3}, []int{4, 5}} [][]Point{{{0, 1}, {1, 2}}} // same as [][]Point{[]Point{Point{0, 1}, Point{1, 2}}} map[string]Point{"orig": {0, 0}} // same as map[string]Point{"orig": Point{0, 0}} map[Point]string{{0, 0}: "orig"} // same as map[Point]string{Point{0, 0}: "orig"}
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 211.6K bytes - Viewed (0) -
src/cmd/cgo/doc.go
by _GoStringPtr. Note that the string contents may not have a trailing NUL byte. As Go doesn't have support for C's union type in the general case, C's union types are represented as a Go byte array with the same length. Go structs cannot embed fields with C types. Go code cannot refer to zero-sized fields that occur at the end of non-empty C structs. To get the address of such a field (which is the
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Sun Mar 31 09:02:45 GMT 2024 - 42.1K bytes - Viewed (0) -
src/cmd/api/api_test.go
required: []string{"A", "B", "C"}, exception: []string{"B"}, ok: true, out: "", }, // Test that a feature required on a subset of ports is implicitly satisfied // by the same feature being implemented on all ports. That is, it shouldn't // say "pkg syscall (darwin-amd64), type RawSockaddrInet6 struct" is missing. // See https://go.dev/issue/4303. {
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Jan 04 17:31:12 GMT 2024 - 7.1K bytes - Viewed (0) -
src/bytes/buffer_test.go
"math/rand" "strconv" "testing" "unicode/utf8" ) const N = 10000 // make this bigger for a larger (and slower) test var testString string // test data for write tests var testBytes []byte // test data; same as testString but as a slice. type negativeReader struct{} func (r *negativeReader) Read([]byte) (int, error) { return -1, nil } func init() { testBytes = make([]byte, N) for i := 0; i < N; i++ {
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Fri Apr 26 13:31:36 GMT 2024 - 18.6K bytes - Viewed (0) -
src/archive/zip/reader_test.go
// } // return buf.Bytes() // } // // The 4 GB of zeros compresses to 4 MB, which compresses to 20 kB, // which compresses to 1252 bytes (in the hex dump below). // // It's here in hex for the same reason as rZipBytes above: to avoid // problems with on-disk virus scanners or other zip processors. func biggestZipBytes() []byte { s := ` 0000000 50 4b 03 04 14 00 08 00 08 00 00 00 00 00 00 00
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Mar 27 18:23:49 GMT 2024 - 55.3K bytes - Viewed (0) -
src/bytes/boundary_test.go
package bytes_test import ( . "bytes" "syscall" "testing" ) // This file tests the situation where byte operations are checking // data very near to a page boundary. We want to make sure those // operations do not read across the boundary and cause a page // fault where they shouldn't. // These tests run only on linux. The code being tested is // not OS-specific, so it does not need to be tested on all // operating systems.
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Nov 30 20:05:58 GMT 2023 - 2.8K bytes - Viewed (0) -
src/bytes/bytes_test.go
if pos != -1 { t.Errorf("IndexByte(%q, 'x') = %v", b1, pos) } } } } // test a small index across all page offsets func TestIndexByteSmall(t *testing.T) { b := make([]byte, 5015) // bigger than a page // Make sure we find the correct byte even when straddling a page. for i := 0; i <= len(b)-15; i++ { for j := 0; j < 15; j++ { b[i+j] = byte(100 + j) } for j := 0; j < 15; j++ {
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Jan 24 16:07:25 GMT 2024 - 56.2K bytes - Viewed (0) -
doc/asm.html
Therefore, to be safe for use with these modes, assembly sources should typically avoid CX except between memory references. </p> <h3 id="amd64">64-bit Intel 386 (a.k.a. amd64)</h3> <p> The two architectures behave largely the same at the assembler level. Assembly code to access the <code>m</code> and <code>g</code> pointers on the 64-bit version is the same as on the 32-bit 386,
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Tue Nov 28 19:15:27 GMT 2023 - 36.3K bytes - Viewed (0)