From 0916a421e04c62bb2a653db7e0d2639bd7ea2711 Mon Sep 17 00:00:00 2001 From: Peter Hinch Date: Fri, 6 Dec 2019 06:23:32 +0000 Subject: [PATCH] uasyncio README: reference low power applications. --- uasyncio_iostream/README.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/uasyncio_iostream/README.md b/uasyncio_iostream/README.md index 70d8a6e..7d9c15c 100644 --- a/uasyncio_iostream/README.md +++ b/uasyncio_iostream/README.md @@ -76,14 +76,13 @@ MicroPython optimised primitives are in `uasyncio/`. Primitives compatible with # 6. Future uasyncio implementations If part of `uasyncio` is to be implemented in C, it would be good if the following -capabilities were retained to facilitate writing efficient add-on modules along the -lines of the `Message` and `Barrier` classes: +capabilities were retained: 1. The ability to subclass the `asyncio` compatible primitives. - 2. The ability to subclass `uasyncio.Primitive` (if you implement it). - 3. Some means of creating awaitable classes (e.g. `__iter__`). - -The mechanism for doing these things might change, but it would be a shame to lose -the capability. + 2. The ability to subclass `uasyncio.Primitive` (or provide other access to that + functionality). + 3. A means of replacing the timebase by one based on the RTC for low power + applications. + 4. A means of creating awaitable classes (e.g. `__iter__`). # 7. Revisiting topics discussed via email