- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for straum (0.17 sec)
-
doc/go1.17_spec.html
a number of productions. Go programs may omit most of these semicolons using the following two rules: </p> <ol> <li> When the input is broken into tokens, a semicolon is automatically inserted into the token stream immediately after a line's final token if that token is <ul> <li>an <a href="#Identifiers">identifier</a> </li> <li>an <a href="#Integer_literals">integer</a>,
HTML - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 211.6K bytes - Viewed (0) -
doc/asm.html
but only worthwhile if it's likely the instruction will be used again. Instead, for simple one-off cases, it's possible to use the <code>BYTE</code> and <code>WORD</code> directives to lay down explicit data into the instruction stream within a <code>TEXT</code>. Here's how the 386 runtime defines the 64-bit atomic load function. </p> <pre> // uint64 atomicload64(uint64 volatile* addr); // so actually
HTML - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Nov 28 19:15:27 GMT 2023 - 36.3K bytes - Viewed (0) -
doc/go_spec.html
a number of productions. Go programs may omit most of these semicolons using the following two rules: </p> <ol> <li> When the input is broken into tokens, a semicolon is automatically inserted into the token stream immediately after a line's final token if that token is <ul> <li>an <a href="#Identifiers">identifier</a> </li> <li>an <a href="#Integer_literals">integer</a>,
HTML - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Fri Apr 26 00:39:16 GMT 2024 - 279.6K bytes - Viewed (0)