Home
last modified time | relevance | path

Searched refs:Go (Results 1 – 25 of 602) sorted by relevance

12345678910>>...25

/external/rust/crates/regex-automata/data/fowler-tests/
Drepetition.dat46 E ((..)|(.)){2} aaa (0,3)(2,3)(0,2)(2,3) RE2/Go
50 E ((..)|(.))* aaa (0,3)(2,3)(0,2)(2,3) RE2/Go
59 E ((..)|(.)){3} aaaa (0,4)(3,4)(0,2)(3,4) RE2/Go
70 E ((..)|(.)){3} aaaaa (0,5)(4,5)(2,4)(4,5) RE2/Go
73 E ((..)|(.))* aaaaa (0,5)(4,5)(2,4)(4,5) RE2/Go
100 :HA#110:E X(.?){0,8}Y X1234567Y (0,9)(8,8) RE2/Go
102 :HA#111:E X(.?){1,8}Y X1234567Y (0,9)(8,8) RE2/Go
104 :HA#112:E X(.?){2,8}Y X1234567Y (0,9)(8,8) RE2/Go
106 :HA#113:E X(.?){3,8}Y X1234567Y (0,9)(8,8) RE2/Go
108 :HA#114:E X(.?){4,8}Y X1234567Y (0,9)(8,8) RE2/Go
[all …]
Dnullsubexpr.dat5 E SAME x (0,0)(?,?) RE2/Go
23 E SAME x (0,0)(?,?) RE2/Go
32 E SAME b (0,0)(?,?) RE2/Go
45 E SAME aaaaaa (0,0)(?,?) RE2/Go
48 E SAME ababab (0,0)(?,?) RE2/Go
69 E (a*)*(x) x (0,1)(?,?)(0,1) RE2/Go
DREADME1 Test data was taken from the Go distribution, which was in turn taken from the
9 The tests themselves were modified for RE2/Go. A couple were modified further
10 by me (Andrew Gallant) (only in repetition.dat) so that RE2/Go would pass them.
11 (Yes, it seems like RE2/Go includes failing test cases.) This may or may not
/external/rust/crates/regex/src/testdata/
Drepetition.dat46 E ((..)|(.)){2} aaa (0,3)(2,3)(0,2)(2,3) RE2/Go
50 E ((..)|(.))* aaa (0,3)(2,3)(0,2)(2,3) RE2/Go
59 E ((..)|(.)){3} aaaa (0,4)(3,4)(0,2)(3,4) RE2/Go
70 E ((..)|(.)){3} aaaaa (0,5)(4,5)(2,4)(4,5) RE2/Go
73 E ((..)|(.))* aaaaa (0,5)(4,5)(2,4)(4,5) RE2/Go
100 :HA#110:E X(.?){0,8}Y X1234567Y (0,9)(8,8) RE2/Go
102 :HA#111:E X(.?){1,8}Y X1234567Y (0,9)(8,8) RE2/Go
104 :HA#112:E X(.?){2,8}Y X1234567Y (0,9)(8,8) RE2/Go
106 :HA#113:E X(.?){3,8}Y X1234567Y (0,9)(8,8) RE2/Go
108 :HA#114:E X(.?){4,8}Y X1234567Y (0,9)(8,8) RE2/Go
[all …]
Dnullsubexpr.dat5 E SAME x (0,0)(?,?) RE2/Go
23 E SAME x (0,0)(?,?) RE2/Go
32 E SAME b (0,0)(?,?) RE2/Go
45 E SAME aaaaaa (0,0)(?,?) RE2/Go
48 E SAME ababab (0,0)(?,?) RE2/Go
69 E (a*)*(x) x (0,1)(?,?)(0,1) RE2/Go
DREADME1 Test data was taken from the Go distribution, which was in turn taken from the
9 The tests themselves were modified for RE2/Go. A couple were modified further
10 by me (Andrew Gallant) (only in repetition.dat) so that RE2/Go would pass them.
11 (Yes, it seems like RE2/Go includes failing test cases.) This may or may not
/external/rust/crates/regex-automata/data/tests/fowler/
Drepetition-long.dat22 :HA#110:E X(.?){0,8}Y X1234567Y (0,9)(8,8) RE2/Go
24 :HA#111:E X(.?){1,8}Y X1234567Y (0,9)(8,8) RE2/Go
26 :HA#112:E X(.?){2,8}Y X1234567Y (0,9)(8,8) RE2/Go
28 :HA#113:E X(.?){3,8}Y X1234567Y (0,9)(8,8) RE2/Go
30 :HA#114:E X(.?){4,8}Y X1234567Y (0,9)(8,8) RE2/Go
32 :HA#115:E X(.?){5,8}Y X1234567Y (0,9)(8,8) RE2/Go
34 :HA#116:E X(.?){6,8}Y X1234567Y (0,9)(8,8) RE2/Go
36 :HA#117:E X(.?){7,8}Y X1234567Y (0,9)(8,8) RE2/Go
65 :HA#280:E (ab|a|c|bcd){0,}(d*) ababcd (0,6)(4,5)(5,6) RE2/Go
67 :HA#281:E (ab|a|c|bcd){1,}(d*) ababcd (0,6)(4,5)(5,6) RE2/Go
[all …]
Drepetition.dat46 E ((..)|(.)){2} aaa (0,3)(2,3)(0,2)(2,3) RE2/Go
50 E ((..)|(.))* aaa (0,3)(2,3)(0,2)(2,3) RE2/Go
59 E ((..)|(.)){3} aaaa (0,4)(3,4)(0,2)(3,4) RE2/Go
70 E ((..)|(.)){3} aaaaa (0,5)(4,5)(2,4)(4,5) RE2/Go
73 E ((..)|(.))* aaaaa (0,5)(4,5)(2,4)(4,5) RE2/Go
Dnullsubexpr.dat5 E SAME x (0,0)(?,?) RE2/Go
23 E SAME x (0,0)(?,?) RE2/Go
32 E SAME b (0,0)(?,?) RE2/Go
45 E SAME aaaaaa (0,0)(?,?) RE2/Go
48 E SAME ababab (0,0)(?,?) RE2/Go
69 E (a*)*(x) x (0,1)(?,?)(0,1) RE2/Go
DREADME1 Test data was taken from the Go distribution, which was in turn taken from the
11 The tests themselves were modified for RE2/Go. A couple were modified further
12 by me (Andrew Gallant) (only in repetition.dat) so that RE2/Go would pass them.
13 (Yes, it seems like RE2/Go includes failing test cases.) This may or may not
/external/flatbuffers/docs/source/
DGoUsage.md1 Use in Go {#flatbuffers_guide_use_go}
6 Before diving into the FlatBuffers usage in Go, it should be noted that
8 to general FlatBuffers usage in all of the supported languages (including Go).
10 Go.
17 ## FlatBuffers Go library code location
19 The code for the FlatBuffers Go library can be found at
23 ## Testing the FlatBuffers Go library
25 The code to test the Go library can be found at `flatbuffers/tests`.
32 *Note: The shell script requires [Go](https://golang.org/doc/install) to
35 ## Using the FlatBuffers Go library
[all …]
/external/pigweed/pw_build/
Dgo.gni15 # This file provides GN build integration for Go. These templates are limited,
21 # Defines a Go package.
23 # A Go package consists of one or more Go files in a single directory. The
24 # package can depend on other Go packages or generated Go code.
27 # sources: List of Go source files.
29 # external_deps: Optional list of Go package dependencies outside of Pigweed.
72 # Builds a Go executable from a Go package.
75 # depend on other Go packages defined in the build.
78 # deps: List of size one specifying the GN path to the Go package target.
79 # package: Name of the Go package as resolved by the Go compiler.
[all …]
/external/clang/test/CodeGenCXX/
Dmangle-local-class-vtables.cpp27 void Go(const I &i);
34 Go(C()); in G()
41 Go(C()); in G()
48 Go(C()); in G()
60 Go(C()); in K()
Dspecialized-static-data-mem-init.cpp19 void Go() { needs_guard.PrintNumK(); } in Go() function
27 C<int>().Go(); in F()
/external/llvm-project/clang/test/CodeGenCXX/
Dmangle-local-class-vtables.cpp27 void Go(const I &i);
34 Go(C()); in G()
41 Go(C()); in G()
48 Go(C()); in G()
60 Go(C()); in K()
/external/oss-fuzz/docs/getting-started/new-project-guide/
Dgo_lang.md3 title: Integrating a Go project
10 # Integrating a Go project
17 The process of integrating a project written in Go with OSS-Fuzz is very similar
20 process. The key specifics of integrating a Go project are outlined below.
22 ## Go-fuzz support
26 only. In that mode, fuzz targets for Go use the libFuzzer engine with native Go
28 libFuzzer command line interface as non-Go fuzz targets.
32 First, you need to write a Go fuzz target that accepts a stream of bytes and
38 projects written in Go. The project files have the following Go specific
76 In order to build a Go fuzz target, you need to call `go-fuzz`
/external/toolchain-utils/go/patch/go-1.11.2/
Dgo1.patch10 // Copyright 2014 The Go Authors. All rights reserved.
20 // Copyright 2011 The Go Authors. All rights reserved.
30 // Copyright 2015 The Go Authors. All rights reserved.
40 // Copyright 2013 The Go Authors. All rights reserved.
50 // Copyright 2015 The Go Authors. All rights reserved.
/external/toolchain-utils/go/patch/go-1.10.3/
Dgo1.patch10 // Copyright 2014 The Go Authors. All rights reserved.
20 // Copyright 2011 The Go Authors. All rights reserved.
30 // Copyright 2015 The Go Authors. All rights reserved.
40 // Copyright 2013 The Go Authors. All rights reserved.
50 // Copyright 2015 The Go Authors. All rights reserved.
/external/starlark-go/doc/
Dimpl.md2 # Starlark in Go: Implementation
5 choices of the Go implementation of Starlark.
56 Not all features of the Go implementation are "standard" (that is,
86 Floating point numbers are represented using Go's `float64`.
100 the Go values that represent them are not hashable in Go: big
102 Consequently, we cannot use Go maps to implement Starlark's dictionary.
111 The `starlarkstruct` Go package provides a non-standard Starlark
131 The Go implementation supports freezing by storing an additional
142 The freeze mechanism in the Go implementation is finer grained than in
150 The Go implementation would also permit the freeze operation to be
[all …]
/external/libcap/psx/
DREADME2 each system call is mirrored on all OS threads of the combined Go/CGo
3 runtime. Since the Go runtime treats OS threads as interchangeable, a
5 (including dropping privilege) in a Go program running on Linux. This
11 build. That release of Go introduced syscall.AllThreadsSyscall*()
/external/toolchain-utils/go/patch/go-1.10.2/
Dgo1.patch10 // Copyright 2014 The Go Authors. All rights reserved.
23 // Copyright 2011 The Go Authors. All rights reserved.
36 // Copyright 2015 The Go Authors. All rights reserved.
49 // Copyright 2013 The Go Authors. All rights reserved.
62 // Copyright 2015 The Go Authors. All rights reserved.
/external/boringssl/src/ssl/test/
DREADME.md11 Instead, we use a fork of the Go `crypto/tls` package, heavily patched with
12 configurable bugs. This code, along with a test suite and harness written in Go,
18 features should be implemented twice, once in C for BoringSSL and once in Go for
19 testing. If possible, the Go code should be suitable for potentially
32 control the Go TLS implementation's behavior.
/external/libcap/
DREADME4 Natively supported languages are C/C++ and Go.
23 installation is required to build the Go packages.
39 the Go packages (if built) under /usr/share/gocode/src
44 Go example programs are to be found in the goapps/ directory. There
/external/golang-protobuf/protoc-gen-go/testdata/imports/
Dtest_import_all.proto1 // Go support for Protocol Buffers - Google's data interchange format
3 // Copyright 2018 The Go Authors. All rights reserved.
38 // test_a_1/m*.proto are in the same Go package and proto package.
39 // test_a_*/*.proto are in different Go packages, but the same proto package.
40 // test_b_1/*.proto are in the same Go package, but different proto packages.
/external/golang-protobuf/
DREADME.md1 # Go support for Protocol Buffers - Google's data interchange format
7 Copyright 2010 The Go Authors.
10 This package and the code it generates requires at least Go 1.9.
12 This software implements Go bindings for protocol buffers. For
21 - Of course, install the Go compiler and tools from
45 generates Go source files that, once compiled, can access and manage
50 There is support for gRPC in Go using protocol buffers.
56 ## Using protocol buffers with Go ##
63 parameter set to the directory you want to output the Go code to.
73 correspond well to the Go notion of packages. In generated Go code,
[all …]

12345678910>>...25