- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for absent (0.21 sec)
-
doc/go1.17_spec.html
field declaration. An empty tag string is equivalent to an absent tag. The tags are made visible through a <a href="/pkg/reflect/#StructTag">reflection interface</a> and take part in <a href="#Type_identity">type identity</a> for structs but are otherwise ignored. </p> <pre> struct { x, y float64 "" // an empty tag string is like an absent tag name string "any string is permitted as a tag"
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
#line 1 "not-str-lit" void __cgo_f_1_5(void) { static const char __cgo_undefined__5[] = (foo); } This program will not compile, but cgo can use the presence or absence of an error message on a given line to deduce the information it needs. The program is syntactically valid regardless of whether each name is a type or an ordinary identifier, so there will be no syntax
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) -
doc/go_spec.html
field declaration. An empty tag string is equivalent to an absent tag. The tags are made visible through a <a href="/pkg/reflect/#StructTag">reflection interface</a> and take part in <a href="#Type_identity">type identity</a> for structs but are otherwise ignored. </p> <pre> struct { x, y float64 "" // an empty tag string is like an absent tag name string "any string is permitted as a tag"
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/cmd/cgo/gcc.go
// We used to look at specific warning or error messages here, but that tied the // behavior too closely to specific versions of the compilers. // Instead, arrange that we can infer what we need from only the presence or absence // of an error on a specific line. // // For each name, we generate these lines, where xxx is the index in toSniff plus one. // // #line xxx "not-declared"
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Nov 02 16:43:23 GMT 2023 - 97K bytes - Viewed (0) -
doc/go_mem.html
unless all the accesses involved are atomic data accesses as provided by the <code>sync/atomic</code> package. As noted already, programmers are strongly encouraged to use appropriate synchronization to avoid data races. In the absence of data races, Go programs behave as if all the goroutines were multiplexed onto a single processor. This property is sometimes referred to as DRF-SC: data-race-free programs execute in a sequentially consistent manner. </p>
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Mon Mar 04 15:54:42 GMT 2024 - 26.6K bytes - Viewed (0)