- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 12 for Bonner (0.15 sec)
-
src/all.bash
Shell Script - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Mon Mar 11 19:53:58 GMT 2024 - 377 bytes - Viewed (0) -
src/archive/tar/common.go
Size int64 // Logical file size in bytes Mode int64 // Permission and mode bits Uid int // User ID of owner Gid int // Group ID of owner Uname string // User name of owner Gname string // Group name of owner // If the Format is unspecified, then Writer.WriteHeader rounds ModTime // to the nearest second and ignores the AccessTime and ChangeTime fields. //
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Fri Mar 15 16:01:50 GMT 2024 - 24.7K bytes - Viewed (2) -
doc/godebug.md
As of Go 1.23 (`winsymlink=1`), mount points no longer have [`os.ModeSymlink`](/pkg/os#ModeSymlink) set, and reparse points that are not symlinks, Unix sockets, or dedup files now always have [`os.ModeIrregular`](/pkg/os#ModeIrregular) set. As a result of these changes, [`filepath.EvalSymlinks`](/pkg/path/filepath#EvalSymlinks) no longer evaluates mount points, which was a source of many inconsistencies and bugs.
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) -
doc/next/6-stdlib/1-time.md
### Timer changes Go 1.23 makes two significant changes to the implementation of [time.Timer] and [time.Ticker]. First, `Timer`s and `Ticker`s that are no longer referred to by the program become eligible for garbage collection immediately, even if their `Stop` methods have not been called. Earlier versions of Go did not collect unstopped `Timer`s until after they had fired and never collected unstopped `Ticker`s.
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Fri Apr 12 20:57:18 GMT 2024 - 1.5K bytes - Viewed (0) -
doc/go_spec.html
<p> Like arrays, slices are always one-dimensional but may be composed to construct higher-dimensional objects. With arrays of arrays, the inner arrays are, by construction, always the same length; however with slices of slices (or arrays of slices), the inner lengths may vary dynamically. Moreover, the inner slices must be initialized individually. </p> <h3 id="Struct_types">Struct types</h3> <p>
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) -
doc/next/6-stdlib/99-minor/path/filepath/63703.md
On Windows, [EvalSymlinks] no longer evaluates mount points, which was a source of many inconsistencies and bugs. This behavior is controlled by the `winsymlink` setting. For Go 1.23, it defaults to `winsymlink=1`. Previous versions default to `winsymlink=0`. On Windows, [EvalSymlinks] no longer tries to normalize volumes to drive letters, which was not always even possible. This behavior is controlled by the `winreadlinkvolume` setting.
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Fri Apr 12 20:57:18 GMT 2024 - 545 bytes - Viewed (0) -
doc/next/6-stdlib/99-minor/os/63703.md
On Windows, [Readlink] no longer tries to normalize volumes to drive letters, which was not always even possible. This behavior is controlled by the `winreadlinkvolume` setting. For Go 1.23, it defaults to `winreadlinkvolume=1`.
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Fri Apr 12 20:57:18 GMT 2024 - 280 bytes - Viewed (0) -
src/buildall.bash
# flag portability issues in builders named "misc-compile" or "all-compile". # As of CL 464955, the build system uses make.bash -compile-only instead, # so this script no longer runs in any automated fashion. # # Options: # -e: stop at first failure if [ ! -f run.bash ]; then echo 'buildall.bash must be run from $GOROOT/src' 1>&2 exit 1 fi sete=false
Shell Script - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Apr 23 17:45:23 GMT 2024 - 2.1K bytes - Viewed (0) -
doc/go_mem.html
In the absence of data races, Go programs behave as if all the goroutines were multiplexed onto a single processor. This property is sometimes referred to as DRF-SC: data-race-free programs execute in a sequentially consistent manner. </p> <p> While programmers should write Go programs without data races, there are limitations to what a Go implementation can do in response to a data race.
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) -
src/cmd/api/main_test.go
if !strings.Contains(f, "(") { return f } return spaceParensRx.ReplaceAllString(f, "") } // portRemoved reports whether the given port-specific API feature is // okay to no longer exist because its port was removed. func portRemoved(feature string) bool { return strings.Contains(feature, "(darwin-386)") || strings.Contains(feature, "(darwin-386-cgo)") }
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Apr 09 20:48:51 GMT 2024 - 31.4K bytes - Viewed (0)