Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for connection (0.18 sec)

  1. src/builtin/builtin.go

    // any pointer.
    type uintptr uintptr
    
    // byte is an alias for uint8 and is equivalent to uint8 in all ways. It is
    // used, by convention, to distinguish byte values from 8-bit unsigned
    // integer values.
    type byte = uint8
    
    // rune is an alias for int32 and is equivalent to int32 in all ways. It is
    // used, by convention, to distinguish character values from integer values.
    type rune = int32
    
    Go
    - Registered: Tue Apr 30 11:13:12 GMT 2024
    - Last Modified: Thu Apr 11 20:22:45 GMT 2024
    - 12.7K bytes
    - Viewed (0)
  2. src/arena/arena.go

    //go:build goexperiment.arenas
    
    /*
    The arena package provides the ability to allocate memory for a collection
    of Go values and free that space manually all at once, safely. The purpose
    of this functionality is to improve efficiency: manually freeing memory
    before a garbage collection delays that cycle. Less frequent cycles means
    the CPU cost of the garbage collector is incurred less frequently.
    
    Go
    - Registered: Tue Apr 30 11:13:12 GMT 2024
    - Last Modified: Wed Oct 12 20:23:36 GMT 2022
    - 4.3K bytes
    - Viewed (0)
  3. src/cmd/cgo/doc.go

    		// Output: 42
    	}
    
    In C, a function argument written as a fixed size array
    actually requires a pointer to the first element of the array.
    C compilers are aware of this calling convention and adjust
    the call accordingly, but Go cannot. In Go, you must pass
    the pointer to the first element explicitly: C.f(&C.x[0]).
    
    Calling variadic C functions is not supported. It is possible to
    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)
  4. misc/cgo/gmp/gmp.go

    Translation of parameters and the return value follows the type
    translation above except that arrays passed as parameters translate
    explicitly in Go to pointers to arrays, as they do (implicitly) in C.
    
    Garbage collection is the big problem.  It is fine for the Go world to
    have pointers into the C world and to free those pointers when they
    are no longer needed.  To help, the Go code can define Go objects
    Go
    - Registered: Tue Apr 30 11:13:12 GMT 2024
    - Last Modified: Mon Apr 11 16:34:30 GMT 2022
    - 9.5K bytes
    - Viewed (0)
Back to top