Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 1,153 for programs (0.55 sec)

  1. src/cmd/vendor/golang.org/x/telemetry/internal/config/config.go

    	ucfg.goversion = set(ucfg.GoVersion)
    	ucfg.program = make(map[string]bool, len(ucfg.Programs))
    	ucfg.pgversion = make(map[pgkey]bool, len(ucfg.Programs))
    	ucfg.pgcounter = make(map[pgkey]bool, len(ucfg.Programs))
    	ucfg.pgcounterprefix = make(map[pgkey]bool, len(ucfg.Programs))
    	ucfg.pgstack = make(map[pgkey]bool, len(ucfg.Programs))
    	ucfg.rate = make(map[pgkey]float64)
    	for _, p := range ucfg.Programs {
    		ucfg.program[p.Name] = true
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Mon Mar 04 17:57:25 UTC 2024
    - 3.5K bytes
    - Viewed (0)
  2. src/os/signal/doc.go

    delivered to the Notify channel, and the write will fail with an EPIPE
    error.
    
    This means that, by default, command line programs will behave like
    typical Unix command line programs, while other programs will not
    crash with SIGPIPE when writing to a closed network connection.
    
    # Go programs that use cgo or SWIG
    
    In a Go program that includes non-Go code, typically C/C++ code
    accessed using cgo or SWIG, Go's startup code normally runs first. It
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Fri Jun 07 18:11:00 UTC 2024
    - 11K bytes
    - Viewed (0)
  3. src/strings/clone.go

    // It guarantees to make a copy of s into a new allocation,
    // which can be important when retaining only a small substring
    // of a much larger string. Using Clone can help such programs
    // use less memory. Of course, since using Clone makes a copy,
    // overuse of Clone can make programs use more memory.
    // Clone should typically be used only rarely, and only when
    // profiling indicates that it is needed.
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Sat May 04 01:23:42 UTC 2024
    - 809 bytes
    - Viewed (0)
  4. src/internal/trace/testdata/README.md

    variable.
    Test names are defined as the name of the `.go` file that generates the
    trace, but with the `.go` extension removed.
    
    ## Trace test programs
    
    The trace test programs in the `testprog` directory generate traces to
    stdout.
    Otherwise they're just normal programs.
    
    ## Trace debug commands
    
    The `cmd` directory contains helpful tools for debugging traces.
    
    * `gotraceraw` parses traces without validation.
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Fri May 17 18:48:18 UTC 2024
    - 1.1K bytes
    - Viewed (0)
  5. src/cmd/vendor/golang.org/x/telemetry/README.md

    ## Notable Packages
    
    - The [x/telemetry/counter](https://pkg.go.dev/golang.org/x/telemetry/counter)
      package provides a library for instrumenting programs with counters and stack
      reports.
    - The [x/telemetry/upload](https://pkg.go.dev/golang.org/x/telemetry/upload)
      package provides a hook for Go toolchain programs to upload telemetry data,
      if the user has opted in to telemetry uploading.
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Mon Mar 04 17:57:25 UTC 2024
    - 2.5K bytes
    - Viewed (0)
  6. doc/go_mem.html

    <p>
    The Go memory model restricts compiler optimizations as much as it does Go programs.
    Some compiler optimizations that would be valid in single-threaded programs are not valid in all Go programs.
    In particular, a compiler must not introduce writes that do not exist in the original program,
    it must not allow a single read to observe multiple values,
    and it must not allow a single write to write multiple values.
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Mon Mar 04 15:54:42 UTC 2024
    - 26.6K bytes
    - Viewed (0)
  7. src/cmd/vendor/golang.org/x/telemetry/internal/upload/reports.go

    		}
    		for _, p := range report.Programs {
    			// does the uploadConfig want this program?
    			// if so, copy over the Stacks and Counters
    			// that the uploadConfig mentions.
    			if !cfg.HasGoVersion(p.GoVersion) || !cfg.HasProgram(p.Program) || !cfg.HasVersion(p.Program, p.Version) {
    				continue
    			}
    			x := &telemetry.ProgramReport{
    				Program:   p.Program,
    				Version:   p.Version,
    				GOOS:      p.GOOS,
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Tue Jun 04 14:52:56 UTC 2024
    - 10.3K bytes
    - Viewed (0)
  8. src/cmd/vendor/golang.org/x/telemetry/internal/telemetry/types.go

    type UploadConfig struct {
    	GOOS       []string
    	GOARCH     []string
    	GoVersion  []string
    	SampleRate float64
    	Programs   []*ProgramConfig
    }
    
    type ProgramConfig struct {
    	// the counter names may have to be
    	// repeated for each program. (e.g., if the counters are in a package
    	// that is used in more than one program.)
    	Name     string
    	Versions []string        // versions present in a counterconfig
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Mon Mar 04 17:10:54 UTC 2024
    - 1.5K bytes
    - Viewed (0)
  9. doc/next/6-stdlib/1-time.md

    now returns 0 instead of 1, which may affect programs that
    poll the length to decide whether a receive on the timer channel
    will succeed.
    Such code should use a non-blocking receive instead.
    
    These new behaviors are only enabled when the main Go program
    is in a module with a `go.mod` `go` line using Go 1.23.0 or later.
    When Go 1.23 builds older programs, the old behaviors remain in effect.
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Thu May 23 20:49:22 UTC 2024
    - 1.5K bytes
    - Viewed (0)
  10. src/cmd/go/testdata/script/godebug_default.txt

    stderr 'panic: panic called with nil argument'
    
    ! go run rsc.io/panicnil
    stderr 'panic: panic called with nil argument'
    
    # Programs in Go 1.20 work module use old panic nil behavior.
    cp go.mod.20 go.mod
    ! go run .
    stderr 'panic: nil'
    
    ! go run rsc.io/panicnil
    stderr 'panic: nil'
    
    # Programs in no module at all should use their go.mod file.
    rm go.mod
    ! go run rsc.io/panicnil@v1.0.0
    stderr 'panic: nil'
    
    rm go.mod
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Wed May 15 13:52:10 UTC 2024
    - 3.5K bytes
    - Viewed (0)
Back to top