- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for mounted (0.18 sec)
-
src/cmd/cgo/doc.go
forth). A Go function called by C code may take C pointers as arguments, and it may store non-pointer data, C pointers, or Go pointers to pinned memory through those pointers. It may not store a Go pointer to unpinned memory in memory pointed to by a C pointer (which again, implies that it may not store a string, slice, channel, and so forth). A Go function called by C code may take a Go pointer but it must preserve the property
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) -
doc/go1.17_spec.html
</p> <ul> <li> <code>x</code> is in the set of values <a href="#Types">determined</a> by <code>T</code>. </li> <li> <code>T</code> is a floating-point type and <code>x</code> can be rounded to <code>T</code>'s precision without overflow. Rounding uses IEEE 754 round-to-even rules but with an IEEE negative zero further simplified to an unsigned zero. Note that constant values never result
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) -
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/go_spec.html
<ul> <li> <code>x</code> is in the set of values <a href="#Types">determined</a> by <code>T</code>. </li> <li> <code>T</code> is a <a href="#Numeric_types">floating-point type</a> and <code>x</code> can be rounded to <code>T</code>'s precision without overflow. Rounding uses IEEE 754 round-to-even rules but with an IEEE negative zero further simplified to an unsigned zero. Note that constant values never result
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/go_mem.html
ahead of the loop in this program: </p> <pre> n := 0 for e := list; e != nil; e = e.next { n++ } i := *p *q = 1 </pre> <p> If <code>list</code> pointed to a cyclic list, then the original program would never access <code>*p</code> or <code>*q</code>, but the rewritten program would. (Moving `*p` ahead would be safe if the compiler can prove `*p` will not panic;
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) -
doc/next/6-stdlib/99-minor/os/61893.md
On Windows, the mode bits reported by [Lstat] and [Stat] for reparse points changed. Mount points no longer have [ModeSymlink] set, and reparse points that are not symlinks, Unix sockets, or dedup files now always have [ModeIrregular] set. This behavior is controlled by the `winsymlink` setting. For Go 1.23, it defaults to `winsymlink=1`.
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Fri Apr 12 20:57:18 GMT 2024 - 386 bytes - Viewed (0)