> `async` to make fake generators.

Genawaiter[0] is one of them.

[0]: https://github.com/whatisaphone/genawaiter

There's also an effort to get generators into the stable language, but it is currently gated on multiple open questions on the async iteration story, including what traits are to be involved (will it be `trait AsyncIteratorItem`? will it wait until GATs and/or async fn in traits and "keyword generics"/"maybe async" functions?), but you can see some explorations of the syntax aspect at https://github.com/estebank/iterator_item/

The proc-macro is written in such a way that it tries to parse as much as possible, so that you can try things out mixing and matching from the different alternatives that I've thought of: https://github.com/estebank/iterator_item/tree/master/tests

Like for example:

    fn foo() => i32 {
        for n in 0..10 {
            yield n;
        }
    }
    fn* foo() -> i32 {
        for n in 0..10 {
            yield n;
        }
    }
    gen foo() -> i32 {
        for n in 0..10 {
            yield n;
        }
    }
    fn* foo() yield i32 {
        for n in 0..10 {
            yield n;
        }
    }

One thing I love about these is how trivially easy it is to turn an Iterator<Item = Future<Output = T>> into an AsyncIterator<Item = T>: https://github.com/estebank/iterator_item/blob/b79d7b496687b...

    async fn* into_stream(input: impl Iterator<Item = Interval>)
        yields Interval
    {
        for i in input {
            yield i;
        }
    }

I'm aware of it, I just find it awkward for some tasks that would be easily expressed using generators in Python or JavaScript.