- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for James (0.15 sec)
-
doc/go1.17_spec.html
identical, and either both functions are variadic or neither is. Parameter and result names are not required to match.</li> <li>Two interface types are identical if they have the same set of methods with the same names and identical function types. <a href="#Exported_identifiers">Non-exported</a> method names from different packages are always different. The order of the methods is irrelevant.</li>
HTML - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 211.6K bytes - Viewed (0) -
doc/asm.html
pseudo-register, not a hardware register, even on architectures with a hardware frame pointer. </p> <p> For assembly functions with Go prototypes, <code>go</code> <code>vet</code> will check that the argument names and offsets match. On 32-bit systems, the low and high 32 bits of a 64-bit value are distinguished by adding a <code>_lo</code> or <code>_hi</code> suffix to the name, as in <code>arg_lo+0(FP)</code> or <code>arg_hi+4(FP)</code>.
HTML - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Tue Nov 28 19:15:27 GMT 2023 - 36.3K bytes - Viewed (0) -
doc/go_spec.html
arguments must be identifiers denoting the type parameters being declared, one for each type parameter of the receiver base type. The type parameter names do not need to match their corresponding parameter names in the receiver base type definition, and all non-blank parameter names must be unique in the receiver parameter section and the method signature. The receiver type parameter constraints are implied by the receiver base type definition:
HTML - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 279.3K bytes - Viewed (0)