</p>

<pre class="ebnf">
ChannelType = ( "chan" | "chan" "&lt;-" | "&lt;-" "chan" ) ElementType .
</pre>

<p>
The optional <code>&lt;-</code> operator specifies the channel <i>direction</i>,
<i>send</i> or <i>receive</i>. If no direction is given, the channel is
<i>bidirectional</i>.
A channel may be constrained only to send or only to receive by
<a href="#Assignments">assignment</a> or

CFLAGS, CPPFLAGS, CXXFLAGS, FFLAGS and LDFLAGS may be defined with pseudo
#cgo directives within these comments to tweak the behavior of the C, C++
or Fortran compiler. Values defined in multiple directives are concatenated
together. The directive can include a list of build constraints limiting its
effect to systems satisfying one of the constraints
(see https://golang.org/pkg/go/build/#hdr-Build_Constraints for details about the constraint syntax).
For example:

		File: []ZipTestFile{
			{
				Name:    "世界",
				Content: []byte{},
				Mode:    0644,
				// Name is valid UTF-8, but format does not have UTF-8 flag set.
				// We don't do UTF-8 detection for multi-byte runes due to
				// false-positives with other encodings (e.g., Shift-JIS).
				// Format says encoding is not UTF-8, so we trust it.
				NonUTF8:  true,

<p>
Global data symbols are defined by a sequence of initializing
<code>DATA</code> directives followed by a <code>GLOBL</code> directive.
Each <code>DATA</code> directive initializes a section of the
corresponding memory.
The memory not explicitly initialized is zeroed.
The general form of the <code>DATA</code> directive is

<pre>
DATA	symbol+offset(SB)/width, value
</pre>

<p>

<pre class="ebnf">
ChannelType = ( "chan" | "chan" "&lt;-" | "&lt;-" "chan" ) ElementType .
</pre>

<p>
The optional <code>&lt;-</code> operator specifies the channel <i>direction</i>,
<i>send</i> or <i>receive</i>. If a direction is given, the channel is <i>directional</i>,
otherwise it is <i>bidirectional</i>.
A channel may be constrained only to send or only to receive by
<a href="#Assignment_statements">assignment</a> or

pkg syscall (freebsd-arm64), const DLT_PPP_WITH_DIR = 204
pkg syscall (freebsd-arm64), const DLT_PPP_WITH_DIR ideal-int
pkg syscall (freebsd-arm64), const DLT_PPP_WITH_DIRECTION = 166
pkg syscall (freebsd-arm64), const DLT_PPP_WITH_DIRECTION ideal-int
pkg syscall (freebsd-arm64), const DLT_PRISM_HEADER = 119
pkg syscall (freebsd-arm64), const DLT_PRISM_HEADER ideal-int
pkg syscall (freebsd-arm64), const DLT_PRONET = 4

        It does not affect the behaviour of proxy.golang.org or the go command.
        Instead we recommend using the retract directive which will be processed by all 3 of the above.

        If you have deleted your repo, please recreate it and publish a retraction.

        Retracting a module version involves adding a retract directive to your go.mod file and publishing a new version.

pkg syscall (freebsd-riscv64), const DLT_PPP_WITH_DIR = 204 #53466
pkg syscall (freebsd-riscv64), const DLT_PPP_WITH_DIR ideal-int #53466
pkg syscall (freebsd-riscv64), const DLT_PPP_WITH_DIRECTION = 166 #53466
pkg syscall (freebsd-riscv64), const DLT_PPP_WITH_DIRECTION ideal-int #53466
pkg syscall (freebsd-riscv64), const DLT_PRISM_HEADER = 119 #53466
pkg syscall (freebsd-riscv64), const DLT_PRISM_HEADER ideal-int #53466

/* An example of writing a C++ virtual function in Go.  */

%module(directors="1") callback

%{
#include <string>
#include "main.h"
%}

%include "std_string.i"

%feature("director");

			// #cgo (nocallback|noescape) <function name>
			if fields := strings.Fields(l); len(fields) == 3 {
				directive := fields[1]
				funcName := fields[2]
				if directive == "nocallback" {
					fatalf("#cgo nocallback disabled until Go 1.23")
					f.NoCallbacks[funcName] = true
				} else if directive == "noescape" {
					fatalf("#cgo noescape disabled until Go 1.23")
					f.NoEscapes[funcName] = true
				}
			}