Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for Explain (0.24 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/go1.17_spec.html

    as a numeric constant: <code>\x</code> followed by exactly two hexadecimal
    digits; <code>\u</code> followed by exactly four hexadecimal digits;
    <code>\U</code> followed by exactly eight hexadecimal digits, and a
    plain backslash <code>\</code> followed by exactly three octal digits.
    In each case the value of the literal is the value represented by
    the digits in the corresponding base.
    </p>
    
    <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)
  3. 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