From 13c6ff76e80383ee6fea558ba6f031714bebd213 Mon Sep 17 00:00:00 2001 From: Marcin Czenko Date: Mon, 30 Jun 2025 15:51:04 +0200 Subject: [PATCH] records some info related to async iterators and their extraction to a separate package --- 10 Notes/Async Iterators.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 10 Notes/Async Iterators.md diff --git a/10 Notes/Async Iterators.md b/10 Notes/Async Iterators.md new file mode 100644 index 0000000..d00879f --- /dev/null +++ b/10 Notes/Async Iterators.md @@ -0,0 +1,15 @@ +--- +related-to: + - "[[Async Iterators can be unsafe in some circumstances]]" +--- +We will be extracting our iterators: `Iter`, `AsyncIter`, and `AsyncResultIter` to a separate package. We will document it here, for now, we are communicating the process and related issues. + +First check this Discord Discussion: + - https://discord.com/channels/895609329053474826/1168926478180810903/1388143470945767587 + - and also here in the relation to https://github.com/status-im/nim-faststreams: https://discord.com/channels/895609329053474826/1168926478180810903/1388145112479170620 + +From those discussions: + +- https://github.com/SirNickolas/asyncIters-Nim +- [asyncIters-Nim](https://github.com/SirNickolas/asyncIters-Nim) +- [Why isn’t `chronosInternalRetFuture` gensymmed?](https://github.com/status-im/nim-chronos/issues/368)