Searched full:future (Results 1 – 25 of 76) sorted by relevance
1234
175 /* strict mode future reserved keywords */183 /* context dependent future */
62 violating the recipe does not currently affect the compilation, in future76 **shrink** it in the future releases based on the feedback from the developers,
208 /* strict mode future reserved keywords */217 /* context dependent future */
18 # get absolute path to linter folder for possible use in future
18 desc: The following identifiers are also treated as keywords and are reserved for the future use (o…
25 // check required in future
19 …'<mutex>' 'pthread' '<shared_mutex>' '<condition_variable>' '<future>' '<stop_token>' 'this_thread'
57 …* Save reference for future processing and handle it with GC point of view (mark needed fields, if…
100 // Future work: add main entry mapping to ai file
30 // by adding `INTARRAY` in the future
63 * @param task_type - TaskType of future TaskQueue.64 * @param vm_type - VMType of future TaskQueue.
87 std::future<bool> compilation_result_future = compilation_result_promise->get_future();
28 # this will be fixed in the future
49 …methods, and bytecodes (built-in code blocks and constant strings in the future) in Actor instance…
74 * loop. We call them phi-candidates (in future they can be used to reuse
180 // Revise it in the future optimizations. in TryInline()
150 // Leave other cases for future including extended simplification of partial expressions in ExtFoldIor()171 // Consider other cases in future in ExtFoldIor()
101 …* @brief Add a coroutine to the finalization queue for future destruction and schedule the next re…
37 …* @brief defines the scheduling policy for a coroutine. Maybe in future we would like to add more …
143 # TODO(liyiming): will support x86_64 in future
26 …C++ base that represent this opcode. In far future if we managed to generate also instruction clas…
161 * support single use in DUInfo in future