Hacker News Reader

Comment by ahepp | Hacker News Reader

Part of me agrees with what you’re saying. I mean, tokio is right there in the namespace.

But another part of me questions why it’s ok that calling a function in the wrong context is a runtime panic rather than a compilation error. Coming from a C background it seems pretty normal to just have a “tokio_context*” argument on tokio functions that would at least make the statefullness less obscure?

View on HN

Is what you're suggesting that one has to pass that `tokio_context` into every `.await()`? If so, I personally would be in strong opposition, cuz I don't think the verbosity cost is justified, in any of the use cases for async I've come across.

I don't think you'd have to pass the context into an await? Await is a Rust construct, not a tokio one. Unless I'm making a complete fool of myself...

Maybe I'm just jaded from writing too much C, but it doesn't seem like a big deal to me to change sleep(duration) to sleep(ctx, duration). Three letters to be correct, transparent, and not have global state? Look at what a complete mess the C standard library is from where they used global state like that.

I'm sure there are lots of other ways you could do it, like make the context it's own struct and call a sleep impl for the struct or something?

Yeah, I guess we're disagreeing about a very non-concrete proposal, so there isn't much point to our convo :)

Reply on news.ycombinator.com