Home
last modified time | relevance | path

Searched full:completion (Results 1 – 25 of 4632) sorted by relevance

12345678910>>...186

/external/clang/test/CodeCompletion/
Dordinary-name.cpp7 …// RUN: %clang_cc1 -fsyntax-only -fcxx-exceptions -code-completion-patterns -code-completion-at=%s…
8 // CHECK-CC1: COMPLETION: bool
9 // CHECK-CC1-NEXT: COMPLETION: char
10 // CHECK-CC1-NEXT: COMPLETION: class
11 // CHECK-CC1-NEXT: COMPLETION: const
12 // CHECK-CC1-NEXT: COMPLETION: Pattern : const_cast<<#type#>>(<#expression#>)
13 // CHECK-CC1: COMPLETION: Pattern : [#void#]delete <#expression#>
14 // CHECK-CC1-NEXT: COMPLETION: Pattern : [#void#]delete [] <#expression#>
15 // CHECK-CC1-NEXT: COMPLETION: Pattern : do{<#statements#>
16 // CHECK-CC1: COMPLETION: double
[all …]
Dordinary-name-cxx11.cpp7 …// RUN: %clang_cc1 -fsyntax-only -fcxx-exceptions -code-completion-patterns -code-completion-at=%s…
8 // CHECK-CC1: COMPLETION: bool
9 // CHECK-CC1-NEXT: COMPLETION: char
10 // CHECK-CC1-NEXT: COMPLETION: char16
11 // CHECK-CC1-NEXT: COMPLETION: char32
12 // CHECK-CC1-NEXT: COMPLETION: class
13 // CHECK-CC1-NEXT: COMPLETION: const
14 // CHECK-CC1-NEXT: COMPLETION: Pattern : const_cast<<#type#>>(<#expression#>)
15 // CHECK-CC1: COMPLETION: Pattern : [#void#]delete <#expression#>
16 // CHECK-CC1-NEXT: COMPLETION: Pattern : [#void#]delete [] <#expression#>
[all …]
Dctor-initializer.cpp3 …// RUN: %clang_cc1 -fsyntax-only -code-completion-at=%s:2:12 %s -o - | FileCheck -check-prefix=CHE…
4 // CHECK-CC1: COMPLETION: Pattern : member1(<#args#>)
5 // CHECK-CC1: COMPLETION: Pattern : member2(<#args#>
8 …// RUN: %clang_cc1 -fsyntax-only -code-completion-at=%s:7:30 %s -o - | FileCheck -check-prefix=CHE…
9 // CHECK-CC2-NOT: COMPLETION: Pattern : member1(<#args#>)
10 // CHECK-CC2: COMPLETION: Pattern : member2(<#args#>
24 // RUN: %clang_cc1 -fsyntax-only -code-completion-at=%s:23:22 %s -o - | FileCheck -check-prefix=CHE…
25 // CHECK-CC3: COMPLETION: Pattern : Base1(<#args#>)
26 // CHECK-CC3: COMPLETION: Pattern : deriv1(<#args#>)
31 // RUN: %clang_cc1 -fsyntax-only -code-completion-at=%s:28:29 %s -o - | FileCheck -check-prefix=CHE…
[all …]
Dobjc-expr.m7 // RUN: %clang_cc1 -fsyntax-only -code-completion-patterns -code-completion-at=%s:4:11 %s -fno-cons…
8 // CHECK-AT: COMPLETION: Pattern : [#NSString *#]"<#string#>"
9 // CHECK-AT: COMPLETION: Pattern : [#id#](<#expression#>)
10 // CHECK-AT: COMPLETION: Pattern : [#NSArray *#][<#objects, ...#>]
11 // CHECK-AT: COMPLETION: Pattern : [#char[]#]encode(<#type-name#>)
12 // CHECK-AT: COMPLETION: Pattern : [#Protocol *#]protocol(<#protocol-name#>)
13 // CHECK-AT: COMPLETION: Pattern : [#SEL#]selector(<#selector#>)
14 // CHECK-AT: COMPLETION: Pattern : [#NSDictionary *#]{<#key#>: <#object, ...#>}
16 // RUN: %clang_cc1 -fsyntax-only -code-completion-patterns -code-completion-at=%s:4:11 %s -fconst-s…
17 // CHECK-CONST-STRINGS: COMPLETION: Pattern : [#const char[]#]encode(<#type-name#>)
Denum-switch-case.c28 …// RUN: %clang_cc1 -fsyntax-only -code-completion-at=%s:19:10 %s -o - | FileCheck -check-prefix=CH…
35 …// RUN: %clang_cc1 -fsyntax-only -code-completion-at=%s:25:10 %s -o - | FileCheck -check-prefix=CH…
36 // CHECK-CC2: COMPLETION: Blue : [#enum Color#]Blue
37 // CHECK-CC2-NEXT: COMPLETION: c2 : [#unsigned int#]c2
38 // CHECK-CC2-NEXT: COMPLETION: color : [#enum Color#]color
39 // CHECK-CC2-NEXT: COMPLETION: Green : [#enum Color#]Green
40 // CHECK-CC2-NEXT: COMPLETION: Indigo : [#enum Color#]Indigo
41 // CHECK-CC2-NEXT: COMPLETION: Orange : [#enum Color#]Orange
42 // CHECK-CC2-NEXT: COMPLETION: Red : [#enum Color#]Red
43 // CHECK-CC2-NEXT: COMPLETION: Pattern : [#size_t#]sizeof(<#expression-or-type#>)
[all …]
Dmacros.c11 …%clang_cc1 -include %S/Inputs/macros.h -fsyntax-only -code-completion-macros -code-completion-at=%… in test()
13 …%clang_cc1 -include %S/Inputs/macros.h -fsyntax-only -code-completion-macros -code-completion-at=%… in test()
16 …%clang_cc1 -include %S/Inputs/macros.h -fsyntax-only -code-completion-macros -code-completion-at=%… in test()
22 …// RUN: %clang_cc1 -include-pch %t -fsyntax-only -code-completion-macros -code-completion-at=%s:12… in test()
23 …// RUN: %clang_cc1 -include-pch %t -fsyntax-only -code-completion-macros -code-completion-at=%s:14… in test()
24 …// RUN: %clang_cc1 -include-pch %t -fsyntax-only -code-completion-macros -code-completion-at=%s:17… in test()
/external/clang/utils/
Dclang-completion-mode.el1 ;;; Clang Code-Completion minor mode, for use with C/Objective-C/C++.
6 ;; completion to provide code completion results for C, Objective-C,
8 ;; code-completion results in a secondary buffer based on the code
15 ;; completion based on Clang. It needs your help to make it better!
17 ;; To use the Clang code completion mode, first make sure that the
20 ;; clang-completion-mode.el somewhere in your Emacs load path. You can
33 ;; (load-library "clang-completion-mode")
37 ;; M-x customize-group RET clang-completion-mode RET
39 ;; Finally, to try Clang-based code completion in a particular buffer,
40 ;; use M-x clang-completion-mode. When "Clang" shows up in the mode
[all …]
/external/sdv/vsomeip/third_party/boost/asio/test/archetypes/
Dasync_ops.hpp41 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 …]
/external/clang/include/clang/Sema/
DCodeCompleteConsumer.h1 //===---- CodeCompleteConsumer.h - Code Completion Interface ----*- C++ -*-===//
32 /// \brief Default priority values for code-completion results based
41 /// \brief Priority for a send-to-super completion.
71 /// \brief Priority value deltas that are added to code-completion results
97 /// priority of a code-completion result.
99 /// \brief Divide by this factor when a code-completion result's type exactly
102 /// \brief Divide by this factor when a code-completion result's type is
109 /// "similar" types for code completion.
129 /// \brief Determine the priority to be given to a macro code completion result
154 /// \brief The context in which code completion occurred, so that the
[all …]
/external/sdv/vsomeip/third_party/boost/asio/doc/requirements/
Dasynchronous_operations.qbk19 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 …]
/external/sdv/vsomeip/third_party/boost/asio/example/cpp11/operations/
Dcomposed_5.cpp26 // 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 …]
Dcomposed_4.cpp26 // 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 …]
Dcomposed_3.cpp26 // 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 …]
Dcomposed_6.cpp28 // 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 …]
/external/sdv/vsomeip/third_party/boost/asio/example/cpp14/operations/
Dcomposed_5.cpp26 // 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 …]
Dcomposed_4.cpp26 // 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 …]
Dcomposed_3.cpp26 // 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 …]
Dcomposed_6.cpp28 // 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 …]
/external/clang/test/Index/
Dcomplete-call.cpp97 // RUN: c-index-test -code-completion-at=%s:47:9 %s | FileCheck -check-prefix=CHECK-CC1 %s
99 // CHECK-CC1: Completion contexts:
109 // RUN: c-index-test -code-completion-at=%s:48:9 %s | FileCheck -check-prefix=CHECK-CC2 %s
112 // CHECK-CC2: Completion contexts:
122 // RUN: c-index-test -code-completion-at=%s:49:9 %s | FileCheck -check-prefix=CHECK-CC3 %s
125 // CHECK-CC3: Completion contexts:
135 // RUN: c-index-test -code-completion-at=%s:49:12 %s | FileCheck -check-prefix=CHECK-CC4 %s
137 // CHECK-CC4: Completion contexts:
147 // RUN: c-index-test -code-completion-at=%s:50:11 %s | FileCheck -check-prefix=CHECK-CC5 %s
149 // CHECK-CC5: Completion contexts:
[all …]
Dcomplete-exprs.c27 // RUN: c-index-test -code-completion-at=%s:7:9 -Xclang -code-completion-patterns %s | FileCheck -c…
28 …=1 CINDEXTEST_COMPLETION_CACHING=1 c-index-test -code-completion-at=%s:7:9 -Xclang -code-completio…
35 …=1 CINDEXTEST_COMPLETION_CACHING=1 c-index-test -code-completion-at=%s:7:9 -Xclang -code-completio…
36 // RUN: c-index-test -code-completion-at=%s:7:14 -Xclang -code-completion-patterns %s | FileCheck -…
37 …1 CINDEXTEST_COMPLETION_CACHING=1 c-index-test -code-completion-at=%s:7:14 -Xclang -code-completio…
44 // RUN: c-index-test -code-completion-at=%s:7:18 -Xclang -code-completion-patterns %s | FileCheck -…
45 // RUN: c-index-test -code-completion-at=%s:7:22 -Xclang -code-completion-patterns %s | FileCheck -…
46 // RUN: c-index-test -code-completion-at=%s:7:2 -Xclang -code-completion-patterns %s | FileCheck -c…
52 // RUN: c-index-test -code-completion-at=%s:11:16 -Xclang -code-completion-patterns %s | FileCheck …
56 // RUN: c-index-test -code-completion-at=%s:19:3 -Xclang -code-completion-patterns %s | FileCheck -…
[all …]
Dcomplete-natural.m11 // RUN: c-index-test -code-completion-at=%s:4:32 %s > %t
14 // CHECK-CC1: Completion contexts:
17 // RUN: c-index-test -code-completion-at=%s:5:18 %s > %t
20 // RUN: c-index-test -code-completion-at=%s:6:7 %s > %t
23 // RUN: c-index-test -code-completion-at=%s:7:7 %s > %t
26 // RUN: c-index-test -code-completion-at=%s:8:10 %s > %t
29 // RUN: c-index-test -code-completion-at=%s:9:9 %s > %t
32 // RUN: c-index-test -code-completion-at=%s:10:19 %s > %t
36 // Same tests as above, but with completion caching.
37 // RUN: env CINDEXTEST_EDITING=1 CINDEXTEST_COMPLETION_CACHING=1 c-index-test -code-completion-at=%…
[all …]
Dcomplete-super.m42 // Check "super" completion as a message receiver.
43 // RUN: c-index-test -code-completion-at=%s:20:4 %s | FileCheck -check-prefix=CHECK-ADD-RECEIVER %s
46 // RUN: c-index-test -code-completion-at=%s:24:4 %s | FileCheck -check-prefix=CHECK-SELECT-RECEIVER…
49 // Check "super" completion at the first identifier
50 // RUN: c-index-test -code-completion-at=%s:20:10 %s | FileCheck -check-prefix=CHECK-ADD-ADD %s
55 // RUN: c-index-test -code-completion-at=%s:24:10 %s | FileCheck -check-prefix=CHECK-SELECTOR-SELEC…
59 // Check "super" completion at the second identifier
60 // RUN: c-index-test -code-completion-at=%s:20:16 %s | FileCheck -check-prefix=CHECK-ADD-TO %s
63 // RUN: c-index-test -code-completion-at=%s:24:28 %s | FileCheck -check-prefix=CHECK-SELECTOR-FIRST…
66 // Check "super" completion at the third identifier
[all …]
/external/grpc-grpc/doc/core/
Dgrpc-cq.md1 # 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 …]
/external/kotlinx.coroutines/kotlinx-coroutines-core/common/src/intrinsics/
DCancellable.kt15 …<T> (suspend () -> T).startCoroutineCancellable(completion: Continuation<T>): Unit = runSafely(com… in <lambda>()
16 … createCoroutineUnintercepted(completion).intercepted().resumeCancellableWith(Result.success(Unit)) in <lambda>()
24 receiver: R, completion: Continuation<T>, in startCoroutineCancellable()
25 ) = runSafely(completion) { in startCoroutineCancellable()
26 …createCoroutineUnintercepted(receiver, completion).intercepted().resumeCancellableWith(Result.succ… in startCoroutineCancellable()
39 * Runs given block and completes completion with its exception if it occurs.
42 * as its cause and resume completion.
44 private inline fun runSafely(completion: Continuation<*>, block: () -> Unit) { in runSafely()
48 dispatcherFailure(completion, e) in runSafely()
52 private fun dispatcherFailure(completion: Continuation<*>, e: Throwable) { in dispatcherFailure()
[all …]
/external/sdv/vsomeip/third_party/boost/asio/doc/overview/
Dasync.qbk32 [:Executes asynchronous operations and queues events on a completion event
36 [mdash] Completion Event Queue
38 [:Buffers completion events until they are dequeued by an asynchronous event
41 [mdash] Completion Handler
48 [:Blocks waiting for events to occur on the completion event queue, and returns
54 the completion handler (i.e. invokes the function object) associated with the
74 executes the asynchronous operation and enqueues the associated completion
75 handler on the completion event queue.]
77 [mdash] Completion Event Queue
79 [:A linked list of completion handlers (i.e. function objects).]
[all …]

12345678910>>...186