Searched refs:future (Results 1 – 10 of 10) sorted by relevance
1 future==0.18.2
143 std::future<bool> getResultFuture() { in getResultFuture()383 std::future<bool> future = callbacks->getResultFuture(); in main() local384 std::future_status status = future.wait_for(std::chrono::seconds(5)); in main()389 success = future.get(); in main()
51 std::future<void> signal = gStopLocationEventsThread.get_future(); in sendLocationEvents()63 std::future<void> signal = gStopMeasurementEventsThread.get_future(); in sendMeasurementEvents()
26 To prevent collision with future common CHRE API definitions, vendor extensions38 prevent collision with future versions of the CHRE API, vendor extensions must48 future use, etc.
271 `<mutex>`, `<atomic>`, `<future>`, etc.298 logging system (a future version of the CHRE API is expected to make logcat
251 working on a reference implementation for a future release. Please reach out via
89 However, a CHRE implementation cannot anticipate all future API changes and
9 CHPP is designed to be flexible and future-proof while meeting the memory and processing constraint…50 …reamble is 0x6843 (“Ch” in ASCII as a little endian 16-bit integer). For future versions, e.g. for…62 Reserved for future use89 …nowledging all packets up to (n-1). The 1-byte ack allows for (optional, future) support of group …
1097 # it is more robust and this tag (HTML_STYLESHEET) will in the future become1107 # standard style sheet and is therefore more robust against future updates.1239 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
