Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for explained (0.42 sec)

  1. src/cmd/cgo/doc.go

    	-srcdir directory
    */
    package main
    
    /*
    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
    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)
  2. doc/asm.html

    If you plan to write assembly language, you should read that document although much of it is Plan 9-specific.
    The current document provides a summary of the syntax and the differences with
    what is explained in that document, and
    describes the peculiarities that apply when writing assembly code to interact with Go.
    </p>
    
    <p>
    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)
  3. doc/go_mem.html

    </p>
    
    <p>
    More generally, it can be shown that any Go program that is data-race-free,
    meaning it has no program executions with read-write or write-write data races,
    can only have outcomes explained by some sequentially consistent interleaving
    of the goroutine executions.
    (The proof is the same as Section 7 of Boehm and Adve's paper cited above.)
    This property is called DRF-SC.
    </p>
    
    <p>
    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)
  4. doc/go_spec.html

    The precise details are relevant for Go implementations,
    affect the specifics of error messages (such as whether
    a compiler reports a type inference or other error),
    and may explain why type inference fails in unusual code situations.
    But by and large these rules can be ignored when writing Go code:
    type inference is designed to mostly "work as expected",
    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)
Back to top