- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 14 for border (0.17 sec)
-
doc/go1.17_spec.html
<a href="#Order_of_evaluation">evaluation order</a>. </p> <p> For struct literals the following rules apply: </p> <ul> <li>A key must be a field name declared in the struct type. </li> <li>An element list that does not contain any keys must list an element for each struct field in the order in which the fields are declared. </li>
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
error messages, debug information, and object files. In practice, parsing these is significantly less work and more robust than parsing C source. Cgo first invokes gcc -E -dM on the preamble, in order to find out about simple #defines for constants and the like. These are recorded for later use. Next, cgo needs to identify the kinds for each identifier. For the identifiers C.foo, cgo generates this C program:
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/archive/zip/reader_test.go
} r, err := f.Open() if err != nil { t.Errorf("%v", err) return } // For very large files, just check that the size is correct. // The content is expected to be all zeros. // Don't bother uncompressing: too big. if ft.Content == nil && ft.File == "" && ft.Size > 0 { if size != ft.Size { t.Errorf("%v: uncompressed size %#x, want %#x", ft.Name, size, ft.Size) } r.Close() return }
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/archive/tar/common.go
// Since the Reader liberally reads some non-compliant files, // it is possible for this to be FormatUnknown. // // If the format is unspecified when Writer.WriteHeader is called, // then it uses the first format (in the order of USTAR, PAX, GNU) // capable of encoding this Header (see Format). Format Format } // sparseEntry represents a Length-sized fragment at Offset in the file. type sparseEntry struct{ Offset, Length int64 }
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Fri Mar 15 16:01:50 GMT 2024 - 24.7K bytes - Viewed (2) -
doc/asm.html
represents the bitwise and instruction, <code>AND</code> (without the leading <code>A</code>), and is written in assembly source as <code>AND</code>. The enumeration is mostly in alphabetical order. (The architecture-independent <code>AXXX</code>, defined in the <code>cmd/internal/obj</code> package, represents an invalid instruction). The sequence of the <code>A</code> names has nothing to do with the actual
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) -
src/cmd/asm/internal/asm/testdata/ppc64.s
XOR $1234567, R5 // 6ca5001268a5d687 XOR $1234567, R5, R3 // 6ca300126863d687 XORIS $15, R3, R4 // 6c64000f XOR $983040, R3, R4 // 6c64000f // TODO: the order of CR operands don't match CMP R3, R4 // 7c232000 CMPU R3, R4 // 7c232040 CMPW R3, R4 // 7c032000 CMPWU R3, R4 // 7c032040
Others - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Apr 24 15:53:25 GMT 2024 - 49K bytes - Viewed (0) -
doc/README.md
new files. **Do not add RELNOTE=yes comments in CLs.** Instead, add a file to the CL (or ask the author to do so). At the end of the development cycle, the files will be merged by being concatenated in sorted order by pathname. Files in the directory matching the glob "*stdlib/*minor" are treated specially. They should be in subdirectories corresponding to standard library package paths, and headings for those package
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Fri Apr 26 21:24:36 GMT 2024 - 1.9K bytes - Viewed (0) -
doc/go_spec.html
<a href="#Order_of_evaluation">evaluation order</a>. </p> <p> For struct literals the following rules apply: </p> <ul> <li>A key must be a field name declared in the struct type. </li> <li>An element list that does not contain any keys must list an element for each struct field in the order in which the fields are declared. </li>
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu May 02 22:43:51 GMT 2024 - 279.6K bytes - Viewed (0) -
src/builtin/builtin.go
// invocation of F then behaves like a call to panic, terminating G's // execution and running any deferred functions. This continues until all // functions in the executing goroutine have stopped, in reverse order. At // that point, the program is terminated with a non-zero exit code. This // termination sequence is called panicking and can be controlled by the // built-in function recover. //
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 12.7K bytes - Viewed (0) -
src/bytes/bytes.go
// returns a slice of subslices of s. If all code points in s satisfy f(c), or // len(s) == 0, an empty slice is returned. // // FieldsFunc makes no guarantees about the order in which it calls f(c) // and assumes that f always returns the same value for a given c. func FieldsFunc(s []byte, f func(rune) bool) [][]byte { // A span is used to record a slice of s of the form s[start:end].
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Mon Feb 19 19:51:15 GMT 2024 - 33.8K bytes - Viewed (0)