- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for declarations (0.05 sec)
-
src/cmd/cgo/doc.go
Using //export in a file places a restriction on the preamble: since it is copied into two different C output files, it must not contain any definitions, only declarations. If a file contains both definitions and declarations, then the two output files will produce duplicate symbols and the linker will fail. To avoid this, definitions must be placed in preambles in other files, or in C source files.
Registered: Tue Sep 09 11:13:09 UTC 2025 - Last Modified: Wed Dec 11 23:57:34 UTC 2024 - 44K bytes - Viewed (0) -
doc/asm.html
which the .s files can then <code>#include</code>. The file contains symbolic <code>#define</code> constants for the offsets of Go struct fields, the sizes of Go struct types, and most Go <code>const</code> declarations defined in the current package. Go assembly should avoid making assumptions about the layout of Go types and instead use these constants. This improves the readability of assembly code, and keeps it robust to
Registered: Tue Sep 09 11:13:09 UTC 2025 - Last Modified: Tue Nov 28 19:15:27 UTC 2023 - 36.3K bytes - Viewed (0) -
src/builtin/builtin.go
type comparable interface{ comparable } // iota is a predeclared identifier representing the untyped integer ordinal // number of the current const specification in a (usually parenthesized) // const declaration. It is zero-indexed. const iota = 0 // Untyped int. // nil is a predeclared identifier representing the zero value for a // pointer, channel, func, interface, map, or slice type.Registered: Tue Sep 09 11:13:09 UTC 2025 - Last Modified: Mon Dec 30 23:59:23 UTC 2024 - 12.8K bytes - Viewed (0)