News for hackers. Stuff that matters.
Re:Rust async-await status report 2 by couchand on Wednesday July 10, 2019 @12:59PM (#20403858)
I'd like to hear about the distinction between promises/futures and async/await. The former is absolutely a useful abstraction, requires no special features to implement, and thus is already widespread. The latter adds syntax support for one particular monad, and in the process adds magic that obscures the fundamental operation.

My experience with JS async/await code in the wild is that developers promptly forget (or never learn) that it desugars to a promise, forget all the tools that can be used for managing complex asynchronous code with explicit promises, and then fail to properly account for the asynchronicity of their code.

I would hope that Rust, with a type system and a community focused on engineering skills, would be able to avoid some of these pitfalls, but I'm not so sure about that.

Re:Rust async-await status report 2 by steveklabnik on Wednesday July 10, 2019 @04:52PM (#20406418)
do notation in a language without a GC is an open research question. Some believe it’s impossible.

However, we have people using Rust today that need help. We could ignore these production users and say “sorry, it’s gonna be who knows when”, or we can ship something that solves their problems. Even shipping async/await itself took four years, even though it’s a technique that’s well known!

Re:Rust async-await status report 2 by couchand on Thursday July 11, 2019 @09:38AM (#20411392)
My working theory is that async/await syntax causes more problems than it solves. I've read through the RFC and many of the comments, but I don't see anywhere a cogent argument why the syntax is needed -- that seems to be taken on faith.

I've written and reviewed boatloads of promise-using JS code, a fair amount of promise-using C++ and task-using C#, and some future-using Rust. I've never seen a case where the value added by async/await exceeds the potential for issues.

The goal seems to be make asynchronous code look like synchronous code. In my experience, developers do in fact act like it's synchronous, forgetting the critical fact that it's not. The supposed feature is a massive bug in everyday usage.

EDIT: reading through the RFC and comments, I now realize that async fn is NOT actually being implemented as sugar on top of future-returning functions, but in fact is more like a Python or ES6 generator. There seems to be a disagreement as to whether an async fn is really just a future-returning function: I see the claim made both ways, and haven't found an authoritative source yet. Confusing!

EDIT2: > do notation in a language without a GC is an open research question. Some believe it’s impossible.

I don't understand how GC comes into play. Isn't the do notation simply syntactic sugar for bind sequencing?

Re:Rust async-await status report 2 by steveklabnik on Thursday July 11, 2019 @11:25AM (#20412257)
> I've never seen a case where the value added by async/await exceeds the potential for issues.

There are many cases in which you can write safe code with async/await that you cannot write safely with raw futures. See here: http://aturon.github.io/tech/2018/04/24/async-borrowing/

> I now realize that async fn is NOT actually being implemented as sugar on top of future-returning functions, but in fact is more like a Python or ES6 generator. There seems to be a disagreement as to whether an async fn is really just a future-returning function: I see the claim made both ways, and haven't found an authoritative source yet. Confusing!

The return type of an `async fn` is an `impl Future`. Additionally, you can `.await` on any `Future` inside of an `async fn`. That means it feels like sugar for Futures, which is why people say that. It's a good mental model. However, the current implementation is a generator internally.

> I don't understand how GC comes into play. Isn't the do notation simply syntactic sugar for bind sequencing?

It is in a language with garbage collection. Things get much more dicey when you don't have those things. For example, Rust has three kinds of closures, not one. You have to deal with references and lifetimes. Rust is generally imperative, and so you have to figure out how break, continue, etc, all work. Due to all of these things and others, the various monadic types Rust have don't actually have the same signatures as each other. I believe there are some more issues, but that's what I've got off the top of my head. That doesn't mean that this is actually impossible; it means that it requires more research to even figure out if it is possible.

Rust doesn't have to solve every problem perfectly. There will be other languages in the future. Maybe Rust++ will have this kind of tech.

Re:Rust async-await status report 2 by couchand on Thursday July 11, 2019 @12:31PM (#20412924)
I had not seen that particular example, thanks for providing the citation.

Perhaps I'm just being stubborn here, but allow me a moment. Isn't the core issue there that the executor requires the future to have a lifetime of 'static? Aaron explains it:

> ...because they are tossed onto executors like thread pools and hence not tied to any particular stack frame.

It's surely a huge undertaking, but wouldn't a more nuanced lifetime analysis solve the underlying problem here? I don't think the issue is that any other way to write this example is unsafe, it's that it's running into a limitation of the borrow checker.

What's required of an asynchronous borrow? The same thing required of any borrow: exclusivity. Sure, the async/await lets you write code that "looks synchronous", and gives the lexical cues the compiler needs to enforce the borrow. But does that mean it's the only way? The counterexample in Aaron's article even relies on async/await! That makes me highly suspicious that the need for it was taken as a given and never sufficiently challenged.

The core issue in that example is that the borrow needs to be held until some point in the future that can't truly be determined lexically. That says to me that it's not a borrow in the traditional Rust model. It is absolutely a useful borrow to check for, but why go about it backwards by only allowing such chronological borrows in such narrow circumstances?

Moreover, the example isn't realistic. The model that should be used for reading from a socket is a stream.

> The return type of an `async fn` is an `impl Future`.

Well, it is and it isn't. For instance, it appears that one can't await on a plain function that returns an `impl Future`...

Re:Rust async-await status report 2 by steveklabnik on Thursday July 11, 2019 @12:49PM (#20413111)
> Isn't the core issue there that the executor requires the future to have a lifetime of 'static?

Yes, and no. That is one of the factors. Another, and IMHO, bigger factor is that the lifetime needs to be 'static only as the task starts to execute. This is why Pin, etc, came into existence. This is due to self-referentiality.

> It's surely a huge undertaking, but wouldn't a more nuanced lifetime analysis solve the underlying problem here?

Yes, we're back in the realm of "open research question."

> What's required of an asynchronous borrow? The same thing required of any borrow: exclusivity.

Most borrows are not exclusive.

> That makes me highly suspicious that the need for it was taken as a given and never sufficiently challenged.

With respect, it is just as easy for me to say "This makes me highly suspicious that you have not investigated how all of this works and that's why you think it's easy."

> The core issue in that example is that the borrow needs to be held until some point in the future that can't truly be determined lexically.

Rust's borrows have not been lexical since last year.

That's fine, of course! It's not like getting into this stuff is easy. But the team working on this has a ton of experience; multiple PhDs, etc, etc. This is the most investigated feature of Rust ever. Again, yes, maybe it is possible, but it's not within the realm of a "just".

Additionally, none of any of the stuff in this comment this solves the original issues with do notation.

> it appears that one can't await on a plain function that returns an `impl Future`...

Sure you can: https://play.rust-lang.org/?version=nightly&mode=debug&editi...

Re:Rust async-await status report 2 by couchand on Thursday July 11, 2019 @01:17PM (#20413387)
> the lifetime needs to be 'static only as the task starts to execute.

It would seem the lifetime needs to be coerceable to the lifetime of the executor, but as far as I can tell never really should need to be 'static.

> Most borrows are not exclusive.

Sorry, I meant, exclusive mutability.

> Rust's borrows have not been lexical since last year.

As I understand it, the borrows are not lexical in the classic sense of lasting until the end of the function, but they are still determined completely lexically, correct? Here the async/await syntax is provide lexical cues regarding the sequencing of asynchronous code, which is how it helps the borrow checker, right?

> But the team working on this has a ton of experience; multiple PhDs, etc, etc.

Of course. You've all done a great job producing a solid language! I'm not questioning the technical chops. And I don't think I said "just", I appreciate the scale of the problem. I'm just arguing about a tradeoff that I have not been able to find much discussion of.

It's great to improve the ergonomics of the language. We need more people to want to use it! Is it possible that this is going too far? It sounds like it introduces an awful lot of magic.

Re:Rust async-await status report 2 by steveklabnik on Thursday July 11, 2019 @01:37PM (#20413571)
> I'm not questioning the technical chops.

No worries then; a lot of people have made very similar statements in the past, and that's the place they're coming from.

> I'm just arguing about a tradeoff that I have not been able to find much discussion of.

I am still not 100% sure what exactly it is you're talking about, at this point, to be honest. I think it's "why do we need async/await and not just write manual futures". I've pointed out several things. Is there something else?

> It would seem the lifetime needs to be coerceable to the lifetime of the executor, but as far as I can tell never really should need to be 'static.

Some executors, like Tokio, are mult-threaded with work-stealing. A task (chain of futures) may start executing on one thread, be waiting, and then get moved to another thread before continuing execution.

> the borrows are not lexical in the classic sense of lasting until the end of the function, but they are still determined completely lexically, correct?

I am not totally sure what you mean by "completely lexically" here. It is true that NLL means that borrows can exist for only part of a lexical scope, but not more than a lexical scope. Or rather, the "more than" part is already taken care of by lifetimes anyway.

> Is it possible that this is going too far? It sounds like it introduces an awful lot of magic.

Most programmers don't really mind magic as much as you'd think. I mean, sure, in some sense, it's a lot of magic, but the result is that instead of writing

    use std::future::Future;
    use std::task::{Context, Poll};
    use std::pin::Pin;
    
    struct Five;
    
    impl Future for Five {
        type Output = i32;
        
        fn poll(self: Pin<&mut Self>, _cx: &mut Context) -> Poll<Self::Output> {
            Poll::Ready(5)        
        }
    }
    
    fn returns_five() -> impl Future<Output=i32> {
        Five 
    }
I write

    async fn returns_five() -> i32 {
        5
    }
And, the intuition that "async fn returns an impl Future that I don't have to implement" is simple enough and accurate enough that it feels like even less magic.

In practice, the people who have been writing tons of networking code don't see it as too much magic; they see it as a significantly nicer way to write the code they already have to write. The ergonomic difference is so large, that the delays in shipping have caused fairly significant community strife and pressure. It is possibly too hyped. Writing manual futures is so, so, so painful.