- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for statement (0.17 sec)
-
doc/go1.17_spec.html
<li>the statement lists in each case, including the default, end in a terminating statement, or a possibly labeled <a href="#Fallthrough_statements">"fallthrough" statement</a>.</li> </ul> </li> <li> A <a href="#Select_statements">"select" statement</a> in which: <ul> <li>there are no "break" statements referring to the "select" statement, and</li>
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_spec.html
<li>the statement lists in each case, including the default, end in a terminating statement, or a possibly labeled <a href="#Fallthrough_statements">"fallthrough" statement</a>.</li> </ul> </li> <li> A <a href="#Select_statements">"select" statement</a> in which: <ul> <li>there are no "break" statements referring to the "select" statement, and</li>
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/ast.go
continue } for _, spec := range d.Specs { if s, ok := spec.(*ast.ImportSpec); ok && s.Path.Value == `"C"` { // Replace "C" with _ "unsafe", to keep program valid. // (Deleting import statement or clause is not safe if it is followed // in the source by an explicit semicolon.) f.Edit.Replace(f.offset(s.Path.Pos()), f.offset(s.Path.End()), `_ "unsafe"`) } } } }
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Jun 07 16:54:27 GMT 2023 - 14.3K bytes - Viewed (0) -
doc/godebug.md
not the older version. To override these defaults, a main package's source files can include one or more `//go:debug` directives at the top of the file (preceding the `package` statement). Continuing the `panicnil` example, if the module or workspace is updated to say `go` `1.21`, the program can opt back into the old `panic(nil)` behavior by including this directive: //go:debug panicnil=1
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Tue Apr 16 17:29:58 GMT 2024 - 13.5K bytes - Viewed (0) -
src/cmd/cgo/doc.go
/* Implementation details. Cgo provides a way for Go programs to call C code linked into the same address space. This comment explains the operation of cgo. Cgo reads a set of Go source files and looks for statements saying import "C". If the import has a doc comment, that comment is taken as literal C code to be used as a preamble to any C code generated by cgo. A typical preamble #includes necessary definitions:
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) -
src/cmd/cgo/gcc.go
// don't want to resolve them to their base types. if *godefs { break } } p.prepareNames(f) if p.rewriteCalls(f) { // Add `import _cgo_unsafe "unsafe"` after the package statement. f.Edit.Insert(f.offset(f.AST.Name.End()), "; import _cgo_unsafe \"unsafe\"") } p.rewriteRef(f) } // loadDefines coerces gcc into spitting out the #defines in use
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
The completion of all <code>init</code> functions is synchronized before the start of the function <code>main.main</code>. </p> <h3 id="go">Goroutine creation</h3> <p class="rule"> The <code>go</code> statement that starts a new goroutine is synchronized before the start of the goroutine's execution. </p> <p> For example, in this program: </p> <pre> var a string func f() { print(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)