- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 11 for describe (0.23 sec)
-
.github/ISSUE_TEMPLATE/11-language-change.yml
description: If so, how does this proposal differ? placeholder: | Yes or No If yes, 1. Mention the related proposals 2. then describe how this proposal differs validations: required: true - type: textarea id: error-handling-proposal attributes: label: Does this affect error handling?
Others - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Wed Nov 22 20:49:24 GMT 2023 - 4.7K bytes - Viewed (0) -
src/cmd/cgo/doc.go
directives, not the environment variables, so that builds work in unmodified environments. Flags obtained from environment variables are not subject to the security limitations described above. All the cgo CPPFLAGS and CFLAGS directives in a package are concatenated and used to compile C files in that package. All the CPPFLAGS and CXXFLAGS
Go - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Sun Mar 31 09:02:45 GMT 2024 - 42.1K bytes - Viewed (0) -
doc/go1.17_spec.html
is the set of all methods declared with receiver <code>*T</code> or <code>T</code> (that is, it also contains the method set of <code>T</code>). Further rules apply to structs containing embedded fields, as described in the section on <a href="#Struct_types">struct types</a>. Any other type has an empty method set. In a method set, each method must have a <a href="#Uniqueness_of_identifiers">unique</a>
HTML - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 211.6K bytes - Viewed (0) -
src/cmd/cgo/gcc.go
case dwarf.TagVariable: name, _ := e.Val(dwarf.AttrName).(string) // As of https://reviews.llvm.org/D123534, clang // now emits DW_TAG_variable DIEs that have // no name (so as to be able to describe the // type and source locations of constant strings) // like the second arg in the call below: // // myfunction(42, "foo") // // If a var has no name we won't see attempts to
Go - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Thu Nov 02 16:43:23 GMT 2023 - 97K bytes - Viewed (0) -
src/archive/tar/common.go
) // FileInfoHeader creates a partially-populated [Header] from fi. // If fi describes a symlink, FileInfoHeader records link as the link target. // If fi describes a directory, a slash is appended to the name. // // Since fs.FileInfo's Name method only returns the base name of // the file it describes, it may be necessary to modify Header.Name // to provide the full path name of the file. //
Go - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Fri Mar 15 16:01:50 GMT 2024 - 24.7K bytes - Viewed (2) -
doc/go_spec.html
interface{ ~[]byte | myString } // bytestring </pre> <p> Note that <code>bytestring</code> is not a real type; it cannot be used to declare variables or compose other types. It exists solely to describe the behavior of some operations that read from a sequence of bytes, which may be a byte slice or a string. </p> <h3 id="Type_identity">Type identity</h3> <p>
HTML - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 279.3K bytes - Viewed (0) -
api/README
Starting with go1.19.txt, each API feature line must end in "#nnnnn" giving the GitHub issue number of the proposal issue that accepted the new API. This helps with our end-of-cycle audit of new APIs. The same requirement applies to next/* (described below), which will become a go1.XX.txt for XX >= 19. The next/ directory contains the only files intended to be mutated. Each file in that directory contains a list of features that may be added
Plain Text - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Wed Jan 31 19:22:50 GMT 2024 - 1.2K bytes - Viewed (0) -
doc/asm.html
If you plan to write assembly language, you should read that document although much of it is Plan 9-specific. The current document provides a summary of the syntax and the differences with what is explained in that document, and describes the peculiarities that apply when writing assembly code to interact with Go. </p> <p> The most important thing to know about Go's assembler is that it is not a direct representation of the underlying machine.
HTML - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Tue Nov 28 19:15:27 GMT 2023 - 36.3K bytes - Viewed (0) -
doc/go_mem.html
published in PLDI 2008. The definition of data-race-free programs and the guarantee of sequential consistency for race-free programs are equivalent to the ones in that work. </p> <p> The memory model describes the requirements on program executions, which are made up of goroutine executions, which in turn are made up of memory operations. </p> <p> A <i>memory operation</i> is modeled by four details: </p> <ul>
HTML - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Mon Mar 04 15:54:42 GMT 2024 - 26.6K bytes - Viewed (0) -
src/archive/tar/reader.go
var gnuLongName, gnuLongLink string // Externally, Next iterates through the tar archive as if it is a series of // files. Internally, the tar format often uses fake "files" to add meta // data that describes the next file. These meta data "files" should not // normally be visible to the outside. As such, this loop iterates through // one or more "header files" until it finds a "normal file".
Go - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Fri Mar 08 01:59:14 GMT 2024 - 26.8K bytes - Viewed (0)