- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for requirements (0.17 sec)
-
src/README.vendor
This is necessary to avoid compiler and linker conflicts. Adding a "vendor/" prefix also maintains the invariant that standard library packages begin with a dotless path element. The module requirements of std and cmd do not influence version selection in other modules. They are only considered when running module commands like 'go get' and 'go mod vendor' from a directory in GOROOT/src. Maintaining vendor directories
Plain Text - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Apr 02 02:20:05 GMT 2024 - 2.2K bytes - Viewed (0) -
src/cmd/cgo/doc.go
file containing it. Then it invokes the host linker (usually gcc) to combine the go.o object file and any supporting non-Go code into a final executable. External linking avoids the dynamic library requirement but introduces a requirement that the host linker be present to create such a binary. Most builds both compile source code and invoke the linker to create a binary. When cgo is involved, the compile step already requires gcc, so
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/go1.17_spec.html
<li>Round to the nearest representable constant if unable to represent a floating-point or complex constant due to limits on precision.</li> </ul> <p> These requirements apply both to literal constants and to the result of evaluating <a href="#Constant_expressions">constant expressions</a>. </p> <h2 id="Variables">Variables</h2> <p>
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) -
doc/go_mem.html
</p> <p> <b>Requirement 1</b>: The memory operations in each goroutine must correspond to a correct sequential execution of that goroutine, given the values read from and written to memory. That execution must be consistent with the <i>sequenced before</i> relation, defined as the partial order requirements set out by the <a href="/ref/spec">Go language specification</a>
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) -
doc/go_spec.html
<li>Round to the nearest representable constant if unable to represent a floating-point or complex constant due to limits on precision.</li> </ul> <p> These requirements apply both to literal constants and to the result of evaluating <a href="#Constant_expressions">constant expressions</a>. </p> <h2 id="Variables">Variables</h2> <p>
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) -
api/README
compatibility. Starting with go1.19.txt, each API feature line must end in "#nnnnn" giving the GitHub issue number of the proposal issue that accepted the new API. This helps with our end-of-cycle audit of new APIs. The same requirement applies to next/* (described below), which will become a go1.XX.txt for XX >= 19. The next/ directory contains the only files intended to be mutated. Each file in that directory contains a list of features that may be added
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Wed Jan 31 19:22:50 GMT 2024 - 1.2K bytes - Viewed (0) -
doc/asm.html
live pointers in its arguments, results, and local stack frame. For an assembly function with no pointer results and either no local stack frame or no function calls, the only requirement is to define a Go prototype for the function in a Go source file in the same package. The name of the assembly function must not contain the package name component (for example,
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)