| /third_party/boost/libs/asio/test/archetypes/ |
| D | async_ops.hpp | 41 void()> completion(token); in BOOST_ASIO_INITFN_RESULT_TYPE() local
44 = boost::asio::get_associated_allocator(completion.completion_handler); in BOOST_ASIO_INITFN_RESULT_TYPE()
47 = boost::asio::get_associated_executor(completion.completion_handler); in BOOST_ASIO_INITFN_RESULT_TYPE()
49 ex.post(BOOST_ASIO_MOVE_CAST(handler_type)(completion.completion_handler), a); in BOOST_ASIO_INITFN_RESULT_TYPE()
51 return completion.result.get(); in BOOST_ASIO_INITFN_RESULT_TYPE()
62 void(boost::system::error_code)> completion(token); in BOOST_ASIO_INITFN_RESULT_TYPE() local
65 = boost::asio::get_associated_allocator(completion.completion_handler); in BOOST_ASIO_INITFN_RESULT_TYPE()
68 = boost::asio::get_associated_executor(completion.completion_handler); in BOOST_ASIO_INITFN_RESULT_TYPE()
74 BOOST_ASIO_MOVE_CAST(handler_type)(completion.completion_handler), in BOOST_ASIO_INITFN_RESULT_TYPE()
81 BOOST_ASIO_MOVE_CAST(handler_type)(completion.completion_handler), in BOOST_ASIO_INITFN_RESULT_TYPE()
[all …]
|
| /third_party/typescript/tests/cases/fourslash/ |
| D | completionListStaticProtectedMembers2.ts | 34 { name: "prototype", sortText: completion.SortText.LocationPriority },
35 { name: "protectedMethod", sortText: completion.SortText.LocalDeclarationPriority },
36 { name: "protectedProperty", sortText: completion.SortText.LocalDeclarationPriority },
37 { name: "publicMethod", sortText: completion.SortText.LocalDeclarationPriority },
38 { name: "publicProperty", sortText: completion.SortText.LocalDeclarationPriority },
39 … { name: "protectedOverriddenMethod", sortText: completion.SortText.LocalDeclarationPriority },
40 … { name: "protectedOverriddenProperty", sortText: completion.SortText.LocalDeclarationPriority},
41 ...completion.functionMembers,
47 { name: "prototype", sortText: completion.SortText.LocationPriority },
48 … { name: "protectedOverriddenMethod", sortText: completion.SortText.LocalDeclarationPriority },
[all …]
|
| D | etsCompletionOfDecoratorName.ts | 12 { name: "Component", sortText: completion.SortText.GlobalsOrKeywords },
13 { name: "Entry", sortText: completion.SortText.GlobalsOrKeywords },
14 { name: "Observed", sortText: completion.SortText.GlobalsOrKeywords },
15 { name: "Preview", sortText: completion.SortText.GlobalsOrKeywords },
16 { name: "State", sortText: completion.SortText.GlobalsOrKeywords },
17 { name: "Prop", sortText: completion.SortText.GlobalsOrKeywords },
18 { name: "Link", sortText: completion.SortText.GlobalsOrKeywords },
19 { name: "ObjectLink", sortText: completion.SortText.GlobalsOrKeywords },
20 { name: "Provide", sortText: completion.SortText.GlobalsOrKeywords },
21 { name: "Consume", sortText: completion.SortText.GlobalsOrKeywords },
[all …]
|
| D | completionListStaticProtectedMembers.ts | 33 { name: "privateMethod", sortText: completion.SortText.LocalDeclarationPriority },
34 { name: "privateProperty", sortText: completion.SortText.LocalDeclarationPriority },
35 { name: "protectedMethod", sortText: completion.SortText.LocalDeclarationPriority },
36 { name: "protectedProperty", sortText: completion.SortText.LocalDeclarationPriority },
37 { name: "publicMethod", sortText: completion.SortText.LocalDeclarationPriority },
38 { name: "publicProperty", sortText: completion.SortText.LocalDeclarationPriority },
39 … { name: "protectedOverriddenMethod", sortText: completion.SortText.LocalDeclarationPriority},
40 … { name: "protectedOverriddenProperty", sortText: completion.SortText.LocalDeclarationPriority }
46 { name: "privateMethod", sortText: completion.SortText.LocalDeclarationPriority },
47 { name: "privateProperty", sortText: completion.SortText.LocalDeclarationPriority },
[all …]
|
| /third_party/FreeBSD/sys/compat/linuxkpi/common/include/linux/ |
| D | completion.h | 29 …* $FreeBSD: releng/12.2/sys/compat/linuxkpi/common/include/linux/completion.h 334427 2018-05-31 12…
49 typedef struct completion { struct
58 /* This inline function should be used to reinitialize a completion structure so it can argument
80 * @ingroup completion
81 * @brief Initialize a completion.
84 * This API is used to initialize a specified completion.
87 …* <li>The input parameter x must point to valid memory, otherwise, initilize a completion would fa…
90 * @param x [IN] Pointer to the completion to be initialized,which must point to valid memory.
94 * <ul><li>completion.h: the header file that contains the API declaration.</li></ul>
97 extern void linux_init_completion(struct completion *x);
[all …]
|
| /third_party/boost/libs/asio/doc/requirements/ |
| D | asynchronous_operations.qbk | 19 asynchronous operation. A ['completion handler] is a function object that will
31 operation, if any, are fully established. The completion handler is submitted
36 [mdash] Event 3: The completion handler is called with the result of the
42 [heading Completion tokens and handlers]
48 [mdash] accept, as the final parameter, a ['completion token] object `token`
51 [mdash] specify a ['completion signature], which is a call signature (C++Std
52 [func.def]) `Signature` that determines the arguments to the completion
56 completion handler function object by performing `typename
58 The completion handler object `completion_handler` is initialized with
66 In this library, all initiating functions specify a ['Completion signature]
[all …]
|
| /third_party/boost/libs/asio/example/cpp11/operations/ |
| D | composed_5.cpp | 26 // an example that works with the Networking TS style of completion tokens,
37 // delivers its result, a completion token also determines the time when the
38 // operation commences. For example, when the completion token is a simple
40 // However, if the completion token's delivery mechanism uses a future, we
49 // completion handler produced by the completion token. This completion
50 // handler matches the asynchronous operation's completion handler signature,
59 // completion token to optimise how they are passed. For example, a lazy
67 // In this example, the composed operation's intermediate completion in operator ()()
72 // The intermediate completion handler holds a reference to the socket so in operator ()()
78 // completion handler is also move-only. in operator ()()
[all …]
|
| D | composed_4.cpp | 26 // an example that works with the Networking TS style of completion tokens,
32 // different completion handler signature. We will also intercept an empty
38 // delivers its result, a completion token also determines the time when the
39 // operation commences. For example, when the completion token is a simple
41 // However, if the completion token's delivery mechanism uses a future, we
50 // completion handler produced by the completion token. This completion
51 // handler matches the asynchronous operation's completion handler signature,
60 // completion token to optimise how they are passed. For example, a lazy
68 // The post operation has a completion handler signature of: in operator ()()
72 // and the async_write operation has a completion handler signature of: in operator ()()
[all …]
|
| D | composed_3.cpp | 26 // an example that works with the Networking TS style of completion tokens,
32 // different completion handler signature. The asynchronous operation
37 // delivers its result, a completion token also determines the time when the
38 // operation commences. For example, when the completion token is a simple
40 // However, if the completion token's delivery mechanism uses a future, we
49 // completion handler produced by the completion token. This completion
50 // handler matches the asynchronous operation's completion handler signature,
59 // completion token to optimise how they are passed. For example, a lazy
67 // The async_write operation has a completion handler signature of: in operator ()()
73 // will adapt our completion handler to async_write's completion handler in operator ()()
[all …]
|
| D | composed_6.cpp | 28 // an example that works with the Networking TS style of completion tokens,
41 // delivers its result, a completion token also determines the time when the
42 // operation commences. For example, when the completion token is a simple
44 // However, if the completion token's delivery mechanism uses a future, we
53 // completion handler produced by the completion token. This completion
54 // handler matches the asynchronous operation's completion handler signature,
63 // completion token to optimise how they are passed. For example, a lazy
72 // In this example, the composed operation's intermediate completion in operator ()()
76 // The intermediate completion handler holds a reference to the socket as in operator ()()
83 // completion handler is also move-only. in operator ()()
[all …]
|
| /third_party/boost/libs/asio/example/cpp14/operations/ |
| D | composed_5.cpp | 26 // an example that works with the Networking TS style of completion tokens,
40 // of CompletionToken type and the completion handler's signature. When the in async_write_message()
41 // completion token is a simple callback, the return type is always void. in async_write_message()
42 // In this example, when the completion token is boost::asio::yield_context in async_write_message()
44 // there is no non-error argument to the completion handler. When the in async_write_message()
45 // completion token is boost::asio::use_future it would be std::future<void>. in async_write_message()
51 // operation delivers its result, a completion token also determines the time in async_write_message()
52 // when the operation commences. For example, when the completion token is a in async_write_message()
54 // returns. However, if the completion token's delivery mechanism uses a in async_write_message()
60 // object's call operator is passed the concrete completion handler produced in async_write_message()
[all …]
|
| D | composed_4.cpp | 26 // an example that works with the Networking TS style of completion tokens,
32 // different completion handler signature. We will also intercept an empty
41 // of CompletionToken type and the completion handler's signature. When the in async_write_message()
42 // completion token is a simple callback, the return type is always void. in async_write_message()
43 // In this example, when the completion token is boost::asio::yield_context in async_write_message()
45 // there is no non-error argument to the completion handler. When the in async_write_message()
46 // completion token is boost::asio::use_future it would be std::future<void>. in async_write_message()
52 // operation delivers its result, a completion token also determines the time in async_write_message()
53 // when the operation commences. For example, when the completion token is a in async_write_message()
55 // returns. However, if the completion token's delivery mechanism uses a in async_write_message()
[all …]
|
| D | composed_3.cpp | 26 // an example that works with the Networking TS style of completion tokens,
32 // different completion handler signature. The asynchronous operation
40 // of CompletionToken type and the completion handler's signature. When the in async_write_message()
41 // completion token is a simple callback, the return type is always void. in async_write_message()
42 // In this example, when the completion token is boost::asio::yield_context in async_write_message()
44 // there is no non-error argument to the completion handler. When the in async_write_message()
45 // completion token is boost::asio::use_future it would be std::future<void>. in async_write_message()
51 // operation delivers its result, a completion token also determines the time in async_write_message()
52 // when the operation commences. For example, when the completion token is a in async_write_message()
54 // returns. However, if the completion token's delivery mechanism uses a in async_write_message()
[all …]
|
| D | composed_6.cpp | 28 // an example that works with the Networking TS style of completion tokens,
45 // of CompletionToken type and the completion handler's signature. When the in async_write_messages()
46 // completion token is a simple callback, the return type is always void. in async_write_messages()
47 // In this example, when the completion token is boost::asio::yield_context in async_write_messages()
49 // there is no non-error argument to the completion handler. When the in async_write_messages()
50 // completion token is boost::asio::use_future it would be std::future<void>. in async_write_messages()
56 // operation delivers its result, a completion token also determines the time in async_write_messages()
57 // when the operation commences. For example, when the completion token is a in async_write_messages()
59 // returns. However, if the completion token's delivery mechanism uses a in async_write_messages()
65 // object's call operator is passed the concrete completion handler produced in async_write_messages()
[all …]
|
| /third_party/boost/doc/html/boost_asio/example/cpp11/operations/ |
| D | composed_5.cpp | 26 // an example that works with the Networking TS style of completion tokens,
37 // delivers its result, a completion token also determines the time when the
38 // operation commences. For example, when the completion token is a simple
40 // However, if the completion token's delivery mechanism uses a future, we
49 // completion handler produced by the completion token. This completion
50 // handler matches the asynchronous operation's completion handler signature,
59 // completion token to optimise how they are passed. For example, a lazy
67 // In this example, the composed operation's intermediate completion in operator ()()
72 // The intermediate completion handler holds a reference to the socket so in operator ()()
78 // completion handler is also move-only. in operator ()()
[all …]
|
| D | composed_4.cpp | 26 // an example that works with the Networking TS style of completion tokens,
32 // different completion handler signature. We will also intercept an empty
38 // delivers its result, a completion token also determines the time when the
39 // operation commences. For example, when the completion token is a simple
41 // However, if the completion token's delivery mechanism uses a future, we
50 // completion handler produced by the completion token. This completion
51 // handler matches the asynchronous operation's completion handler signature,
60 // completion token to optimise how they are passed. For example, a lazy
68 // The post operation has a completion handler signature of: in operator ()()
72 // and the async_write operation has a completion handler signature of: in operator ()()
[all …]
|
| D | composed_3.cpp | 26 // an example that works with the Networking TS style of completion tokens,
32 // different completion handler signature. The asynchronous operation
37 // delivers its result, a completion token also determines the time when the
38 // operation commences. For example, when the completion token is a simple
40 // However, if the completion token's delivery mechanism uses a future, we
49 // completion handler produced by the completion token. This completion
50 // handler matches the asynchronous operation's completion handler signature,
59 // completion token to optimise how they are passed. For example, a lazy
67 // The async_write operation has a completion handler signature of: in operator ()()
73 // will adapt our completion handler to async_write's completion handler in operator ()()
[all …]
|
| D | composed_6.cpp | 28 // an example that works with the Networking TS style of completion tokens,
41 // delivers its result, a completion token also determines the time when the
42 // operation commences. For example, when the completion token is a simple
44 // However, if the completion token's delivery mechanism uses a future, we
53 // completion handler produced by the completion token. This completion
54 // handler matches the asynchronous operation's completion handler signature,
63 // completion token to optimise how they are passed. For example, a lazy
72 // In this example, the composed operation's intermediate completion in operator ()()
76 // The intermediate completion handler holds a reference to the socket as in operator ()()
83 // completion handler is also move-only. in operator ()()
[all …]
|
| /third_party/boost/doc/html/boost_asio/example/cpp14/operations/ |
| D | composed_5.cpp | 26 // an example that works with the Networking TS style of completion tokens,
40 // of CompletionToken type and the completion handler's signature. When the in async_write_message()
41 // completion token is a simple callback, the return type is always void. in async_write_message()
42 // In this example, when the completion token is boost::asio::yield_context in async_write_message()
44 // there is no non-error argument to the completion handler. When the in async_write_message()
45 // completion token is boost::asio::use_future it would be std::future<void>. in async_write_message()
51 // operation delivers its result, a completion token also determines the time in async_write_message()
52 // when the operation commences. For example, when the completion token is a in async_write_message()
54 // returns. However, if the completion token's delivery mechanism uses a in async_write_message()
60 // object's call operator is passed the concrete completion handler produced in async_write_message()
[all …]
|
| D | composed_4.cpp | 26 // an example that works with the Networking TS style of completion tokens,
32 // different completion handler signature. We will also intercept an empty
41 // of CompletionToken type and the completion handler's signature. When the in async_write_message()
42 // completion token is a simple callback, the return type is always void. in async_write_message()
43 // In this example, when the completion token is boost::asio::yield_context in async_write_message()
45 // there is no non-error argument to the completion handler. When the in async_write_message()
46 // completion token is boost::asio::use_future it would be std::future<void>. in async_write_message()
52 // operation delivers its result, a completion token also determines the time in async_write_message()
53 // when the operation commences. For example, when the completion token is a in async_write_message()
55 // returns. However, if the completion token's delivery mechanism uses a in async_write_message()
[all …]
|
| D | composed_3.cpp | 26 // an example that works with the Networking TS style of completion tokens,
32 // different completion handler signature. The asynchronous operation
40 // of CompletionToken type and the completion handler's signature. When the in async_write_message()
41 // completion token is a simple callback, the return type is always void. in async_write_message()
42 // In this example, when the completion token is boost::asio::yield_context in async_write_message()
44 // there is no non-error argument to the completion handler. When the in async_write_message()
45 // completion token is boost::asio::use_future it would be std::future<void>. in async_write_message()
51 // operation delivers its result, a completion token also determines the time in async_write_message()
52 // when the operation commences. For example, when the completion token is a in async_write_message()
54 // returns. However, if the completion token's delivery mechanism uses a in async_write_message()
[all …]
|
| D | composed_6.cpp | 28 // an example that works with the Networking TS style of completion tokens,
45 // of CompletionToken type and the completion handler's signature. When the in async_write_messages()
46 // completion token is a simple callback, the return type is always void. in async_write_messages()
47 // In this example, when the completion token is boost::asio::yield_context in async_write_messages()
49 // there is no non-error argument to the completion handler. When the in async_write_messages()
50 // completion token is boost::asio::use_future it would be std::future<void>. in async_write_messages()
56 // operation delivers its result, a completion token also determines the time in async_write_messages()
57 // when the operation commences. For example, when the completion token is a in async_write_messages()
59 // returns. However, if the completion token's delivery mechanism uses a in async_write_messages()
65 // object's call operator is passed the concrete completion handler produced in async_write_messages()
[all …]
|
| /third_party/grpc/doc/core/ |
| D | grpc-cq.md | 1 # gRPC Completion Queue
7 …is document gives an overview of completion queue architecture and focuses mainly on the interacti…
9 ## Completion queue attributes
10 Completion queue has two attributes
20 …by the grpc-server code to not associate any listening sockets with this completion-queue’s pollset
34 \\ 1. If an event is queued in the completion queue, dequeue and return
37 \\ 2. If completion queue shutdown return
43 \\ it would have scheduled those closures (which may queue completion events
44 \\ on SOME completion queue - not necessarily this one)
49 ### Queuing a completion event (i.e., "tag")
[all …]
|
| /third_party/node/deps/npm/docs/content/cli-commands/ |
| D | npm-completion.md | 3 title: npm-completion
4 description: Tab Completion for npm
7 # npm-completion(1)
9 ## Tab Completion for npm
13 source <(npm completion)
18 Enables tab-completion in all npm commands.
26 npm completion >> ~/.bashrc
27 npm completion >> ~/.zshrc
30 You may of course also pipe the output of `npm completion` to a file
36 environment, `npm completion` acts in "plumbing mode", and outputs
|
| /third_party/node/deps/npm/man/man1/ |
| D | npm-completion.1 | 1 .TH "NPM\-COMPLETION" "1" "April 2022" "" ""
3 \fBnpm-completion\fR \- Tab Completion for npm
8 source <(npm completion)
13 Enables tab\-completion in all npm commands\.
22 npm completion >> ~/\.bashrc
23 npm completion >> ~/\.zshrc
27 You may of course also pipe the output of \fBnpm completion\fP to a file
33 environment, \fBnpm completion\fP acts in "plumbing mode", and outputs
|