Home
last modified time | relevance | path

Searched full:implementations (Results 1 – 25 of 10700) sorted by relevance

12345678910>>...428

/external/perfetto/src/trace_processor/sqlite/bindings/
Dsqlite_module.h32 // Specifies the type of module: implementations can override this field by
42 // implementations can override this field by declaring and defining it.
48 // implementations can override this field by declaring and defining it.
53 // Specifies the type of context for the module. Implementations should define
60 // Implementations should define this type to match the vtab type they use in
66 // Implementations should define this type to match the cursor type they use
72 // Implementations MUST define this function themselves if
84 // Implementations MUST define this function themselves if
92 // Implementations MUST define this function themselves; this function is
103 // Implementations MUST define this function themselves; this function is
[all …]
/external/grpc-grpc/src/python/grpcio_tests/tests/unit/beta/
D_implementations_test.py14 """Tests the implementations module of the gRPC Python Beta API."""
19 from grpc.beta import implementations
27 channel_credentials = implementations.ssl_channel_credentials()
29 channel_credentials, implementations.ChannelCredentials
33 channel_credentials = implementations.ssl_channel_credentials(
37 channel_credentials, implementations.ChannelCredentials
52 call_creds = implementations.google_call_credentials(creds)
53 self.assertIsInstance(call_creds, implementations.CallCredentials)
56 call_creds = implementations.access_token_call_credentials("token")
57 self.assertIsInstance(call_creds, implementations.CallCredentials)
D_beta_features_test.py19 from grpc.beta import implementations
170 server_options = implementations.server_options(
173 self._server = implementations.server(
176 server_credentials = implementations.ssl_server_credentials(
186 self._channel_credentials = implementations.ssl_channel_credentials(
189 self._call_credentials = implementations.metadata_call_credentials(
195 stub_options = implementations.stub_options(
198 self._dynamic_stub = implementations.dynamic_stub(
333 self._server_options = implementations.server_options(
336 self._server_credentials = implementations.ssl_server_credentials(
[all …]
/external/mbedtls/docs/architecture/
Dalternative-implementations.md1 Alternative implementations of Mbed TLS functionality
12 …n alternative implementation during the platform setup](#alternative-implementations-of-platform-f…
16 … [declare an alternative implementation of the timing module](#module-alternative-implementations).
18 …eclare an alternative implementation of the threading module](#module-alternative-implementations).
22 For networking, the `net_sockets` module does not currently support alternative implementations. If…
24 …ding module(s)](#module-alternative-implementations) or [of specific functions](#function-alternat…
32 ## Module alternative implementations
34 …es (threading, timing). Such custom implementations are called “alternative implementations”, or “…
45 Generally, alternative implementations can define their context types to any C type except incomple…
64 …f a context does not remain valid across function calls. Alternative implementations do not need t…
[all …]
/external/federated-compute/fcp/client/http/
Dhttp_client.h54 // cases implementations should ideally handle multiple requests in parallel, at
63 // * Implementations must support at least HTTP/1.1 over TLS 1.2.
64 // * Implementations are also allowed to serve requests using HTTP/2, QUIC or
66 // * Implementations must support both IPv4 and IPv6 (but they are allowed to
69 // * Implementations are responsible for TLS certificate validation and for
72 // * Implementations should not include user-added CAs, and should consider
76 // * Implementations must not supply any cookies in requests (beyond those
78 // * Implementations must not store any cookies returned by the server.
82 // * Implementations must follow HTTP redirects responses, up to an
88 // * Implementations should not implement a cache as it is expected that
[all …]
/external/rust/beto-rust/nearby/crypto/
DREADME.md3 A crypto provider that abstracts over different crypto implementations, mainly the Rust
4 implementations by [RustCrypto](https://github.com/RustCrypto) and BoringSSL.
10 Our own abstraction on top of crypto implementations, including functionalities
13 Two implementations are currently provided, `crypto_provider_rustcrypto` and
19 Since we know we'll have multiple AES implementations in practice (an embedded
26 Implementations of `crypto_provider` types using the convenient pure-Rust primitives
31 Implementations of `crypto_provider` types using the
/external/anonymous-counting-tokens/act/
Dact.h35 // Implementations should return a fresh set of Server parameters
40 // Implementations should return a fresh set of Client parameters
46 // Implementations should verify the consistency of these
54 // Implementations should generate a tuple of client_fingerprints,
65 // Implementations should return OkStatus on a valid request.
74 // Implementations should return the TokensResponse.
82 // Implementations should return OkStatus on a valid response.
93 // Implementations should return a vector of tokens corresponding to the
105 // Implementations should return OkStatus on valid tokens.
/external/libwebm/
DPATENTS.TXT4 "These implementations" means the copyrightable works that implement the WebM
10 run, modify and propagate the contents of these implementations of WebM, where
13 infringed by these implementations of WebM. This grant does not include claims
15 implementations. If you or your agent or exclusive licensee institute or order
18 counterclaim in a lawsuit) alleging that any of these implementations of WebM
19 or any code incorporated within any of these implementations of WebM
22 for these implementations of WebM shall terminate as of the date such
/external/libvpx/
DPATENTS4 "These implementations" means the copyrightable works that implement the WebM
10 run, modify and propagate the contents of these implementations of WebM, where
13 infringed by these implementations of WebM. This grant does not include claims
15 implementations. If you or your agent or exclusive licensee institute or order
18 counterclaim in a lawsuit) alleging that any of these implementations of WebM
19 or any code incorporated within any of these implementations of WebM
22 for these implementations of WebM shall terminate as of the date such
/external/webp/
DPATENTS4 "These implementations" means the copyrightable works that implement the WebM
10 run, modify and propagate the contents of these implementations of WebM, where
13 infringed by these implementations of WebM. This grant does not include claims
15 implementations. If you or your agent or exclusive licensee institute or order
18 counterclaim in a lawsuit) alleging that any of these implementations of WebM
19 or any code incorporated within any of these implementations of WebM
22 for these implementations of WebM shall terminate as of the date such
DLICENSE34 "These implementations" means the copyrightable works that implement the WebM
40 run, modify and propagate the contents of these implementations of WebM, where
43 infringed by these implementations of WebM. This grant does not include claims
45 implementations. If you or your agent or exclusive licensee institute or order
48 counterclaim in a lawsuit) alleging that any of these implementations of WebM
49 or any code incorporated within any of these implementations of WebM
52 for these implementations of WebM shall terminate as of the date such
/external/libvpx/third_party/libwebm/
DPATENTS.TXT4 "These implementations" means the copyrightable works that implement the WebM
10 run, modify and propagate the contents of these implementations of WebM, where
13 infringed by these implementations of WebM. This grant does not include claims
15 implementations. If you or your agent or exclusive licensee institute or order
18 counterclaim in a lawsuit) alleging that any of these implementations of WebM
19 or any code incorporated within any of these implementations of WebM
22 for these implementations of WebM shall terminate as of the date such
/external/libaom/third_party/libwebm/
DPATENTS.TXT4 "These implementations" means the copyrightable works that implement the WebM
10 run, modify and propagate the contents of these implementations of WebM, where
13 infringed by these implementations of WebM. This grant does not include claims
15 implementations. If you or your agent or exclusive licensee institute or order
18 counterclaim in a lawsuit) alleging that any of these implementations of WebM
19 or any code incorporated within any of these implementations of WebM
22 for these implementations of WebM shall terminate as of the date such
/external/threetenbp/src/main/java/org/threeten/bp/temporal/
DTemporal.java65 * There are many reasons for this, part of which is that implementations
97 * This interface places no restrictions on the mutability of implementations,
99 * All implementations must be {@link Comparable}.
111 * Implementations must check and handle all fields defined in {@link ChronoUnit}.
118 * Implementations must not alter this object.
144 * Implementations must not alter either this object.
146 * This provides equivalent, safe behavior for immutable and mutable implementations.
168 * Implementations must check and handle all fields defined in {@link ChronoField}.
176 * Implementations must not alter either this object or the specified temporal object.
178 * This provides equivalent, safe behavior for immutable and mutable implementations.
[all …]
DTemporalAccessor.java64 * There are many reasons for this, part of which is that implementations
69 * This interface places no restrictions on the mutability of implementations,
82 * Implementations must check and handle all fields defined in {@link ChronoField}.
89 * Implementations must not alter this object.
110 * Implementations must check and handle all fields defined in {@link ChronoField}.
118 * Implementations must not alter either this object.
135 * Implementations must check and handle all fields defined in {@link ChronoField}.
144 * Implementations must not alter either this object.
164 * Implementations must check and handle all fields defined in {@link ChronoField}.
172 * Implementations must not alter either this object.
[all …]
/external/mesa3d/src/gfxstream/
DREADME.md70 - Backend implementations
71 - Implementations of the host side of various transports
77 - Implementations of the guest side of various transports (above the kernel)
80 - Implementations of the guest side of various transports (above the kernel)
84 - `protocols/`: implementations of protocols for various graphics APIs. May contain
86 - `host-common/`: implementations of host-side support code that makes it
88 Contains concrete implementations of auxiliary virtual devices such as
90 - `stream-servers/`: implementations of various backends for various graphics
/external/openthread/third_party/mbedtls/repo/docs/architecture/
Dpsa-crypto-implementation-structure.md15implementations through the same C interface reduces the core code size and its call graph complex…
16 …nization of the software cryptographic implementations in drivers promotes modularization of those…
18 …a natural framework to integrate third party or alternative software implementations of cryptograp…
52implementations of `psa_driver_wrapper_<entry_point>` functions are generated by the build system …
54 …celerator drivers, secure element drivers as well as to the software implementations of cryptograp…
60 …y_creation(), psa_finish_key_creation() and psa_fail_key_creation(). Implementations of key creati…
/external/google-cloud-java/java-grafeas/src/main/java/io/grafeas/v1/
DAttestationOccurrenceOrBuilder.java45 * One or more signatures over `serialized_payload`. Verifier implementations
58 * One or more signatures over `serialized_payload`. Verifier implementations
71 * One or more signatures over `serialized_payload`. Verifier implementations
84 * One or more signatures over `serialized_payload`. Verifier implementations
97 * One or more signatures over `serialized_payload`. Verifier implementations
119 * implementations. The JWT itself is opaque to Grafeas.
137 * implementations. The JWT itself is opaque to Grafeas.
155 * implementations. The JWT itself is opaque to Grafeas.
173 * implementations. The JWT itself is opaque to Grafeas.
191 * implementations. The JWT itself is opaque to Grafeas.
DAttestationOccurrence.java106 * One or more signatures over `serialized_payload`. Verifier implementations
122 * One or more signatures over `serialized_payload`. Verifier implementations
138 * One or more signatures over `serialized_payload`. Verifier implementations
154 * One or more signatures over `serialized_payload`. Verifier implementations
170 * One or more signatures over `serialized_payload`. Verifier implementations
199 * implementations. The JWT itself is opaque to Grafeas.
220 * implementations. The JWT itself is opaque to Grafeas.
241 * implementations. The JWT itself is opaque to Grafeas.
262 * implementations. The JWT itself is opaque to Grafeas.
283 * implementations. The JWT itself is opaque to Grafeas.
[all …]
/external/rust/beto-rust/nearby/crypto/crypto_provider_boringssl/src/
Dlib.rs32 /// Implementations of crypto_provider::hkdf traits backed by BoringSSL
35 /// Implementations of crypto_provider::hmac traits backed by BoringSSL
38 /// Implementations of crypto_provider::ed25519 traits backed by BoringSSL
41 /// Implementations of crypto_provider::aead traits backed by BoringSSL
44 /// Implementations of crypto_provider::p256 traits backed by BoringSSL
47 /// Implementations of crypto_provider::x25519 traits backed by BoringSSL
50 /// Implementations of crypto_provider::sha2 traits backed by BoringSSL
/external/rust/crates/gdbstub_arch/src/
Dlib.rs1 //! Community-created implementations of [`gdbstub::arch::Arch`] for various
9 //! Please consider upstreaming any missing `Arch` implementations you happen to
14 //! **Disclaimer:** These implementations are all community contributions, and
17 //! spot a bug in any of the implementations, please file an issue / open a PR!
27 //! upstreamed their `Arch` implementations, and as a result, there are several
28 //! built-in arch implementations which are missing proper `RegId` enums
31 //! As a stop-gap measure, affected `Arch` implementations have been modified to
/external/eigen/unsupported/Eigen/src/SpecialFunctions/
DBesselFunctionsArrayAPI.h24 * other scalar types, the user has to provide implementations of i0(T) for
47 * other scalar types, the user has to provide implementations of i0e(T) for
69 * other scalar types, the user has to provide implementations of i1(T) for
92 * other scalar types, the user has to provide implementations of i1e(T) for
114 * other scalar types, the user has to provide implementations of k0(T) for
137 * other scalar types, the user has to provide implementations of k0e(T) for
159 * other scalar types, the user has to provide implementations of k1(T) for
182 * other scalar types, the user has to provide implementations of k1e(T) for
204 * other scalar types, the user has to provide implementations of j0(T) for
226 * other scalar types, the user has to provide implementations of y0(T) for
[all …]
/external/jazzer-api/src/main/java/com/code_intelligence/jazzer/mutation/api/
DSerializer.java43 * <p>Implementations
52 * @throws IOException declared, but must not be thrown by implementations unless methods called
67 * @throws IOException declared, but must not be thrown by implementations unless methods called
76 * <p>The default implementations call extends the stream with null bytes and then calls
79 * <p>Implementations
88 * @throws IOException declared, but must not be thrown by implementations unless methods called
100 * <p>The default implementations calls through to {@link #read(DataInputStream)} and should only
110 * @throws IOException declared, but must not be thrown by implementations unless methods called
/external/grpc-grpc/doc/
DPROTOCOL-HTTP2.md53 …ones starting with ":" appear before all other headers. Additionally implementations should send *…
55 **Path** is case-sensitive. Some gRPC implementations may allow the **Path**
62 If **Timeout** is omitted a server should assume an infinite timeout. Client implementations are fr…
68 …d using Base64 as per https://tools.ietf.org/html/rfc4648#section-4. Implementations MUST accept p…
73 Implementations must split **Binary-Header**s on "," before decoding the
78 character range defined is stricter than HTTP. Implementations must not error
88 suggested. Implementations are encouraged to compute total header size like
100 …ed. Compression contexts are NOT maintained over message boundaries, implementations must create a…
102 …**Request** stream needs to be closed but no data remains to be sent implementations MUST send an …
121 Implementations should expect broken deployments to send non-200 HTTP status codes in responses as …
[all …]
/external/rust/crates/pin-project-lite/tests/ui/pin_project/
Dconflict-unpin.rs13 // conflicting implementations
26 // conflicting implementations
37 // conflicting implementations
49 // conflicting implementations
61 // conflicting implementations

12345678910>>...428