Viewing profile — aturon

> Trying to change it's role into "marketing/communication/project management tool" out of a sudden FWIW, this was part of the story from the beginning ( https://github.com/rust-la…

Yes, it could! There aren't plans to do so yet, but it'd be worth spinning up a thread on internals about this.

I think the domains of use will be quite different. Since Rust doesn't require a GC or other runtime support, we envision it being used in specific modules to provide a boost to co…

There are changes that require a new edition, particularly around new keywords. However, to be clear, editions are primarily a marketing/communication/project management tool. They…

Yeah, it's really hard to strike the right balance here, and we're constantly learning from experience. Sorry for the pain! I'll put a note on the core team agenda to undergo a rou…

You can track the full status here: https://github.com/rust-lang/rust-roadmap/issues/17

Yes, and that's definitely something we hope to address with the Blitz, both by beefing up top-level library docs, and through the Cookbook.

Rust's goal is to make it easier to write fast, reliable software. It's not just targeted at C/C++ folks. The Rust team often hears from people who have been pulling their hair out…

The new book will be published by NoStarch press!

The key problem: in-memory data structures can embed ownership of system resources.

The intent wasn't to say that we should be seeing big production use right this second , but rather to set out an overall "north star" for work on Rust. The investments in Rust tod…

Thanks for this comment! I actually totally agree with this perspective, and wish I'd used your suggested scale in the post.

Panics are caught at the "task" level -- and there's usually one task per connection. They don't take down the entire server (since tasks are isolation boundaries). Right now, noth…

Yep, same here -- at least for fasthttp. This is pretty far into microbenchmarking territory, so the differences among the top libraries likely don't matter much in practice. But I…

No, it's more related to the fact that Rust allows you to use traits in both a statically- and dynamically-dispatched way. You can read some more on the topic here: http://aturon.g…

Thanks for the thoughtful reply! I'm a little confused about the snippet you're pointing out. It's not actually using futures at all! In fact, that code is just part of setting up …

This is an exciting upcoming feature in Rust, which you can read more about in a couple places: - http://aturon.github.io/blog/2015/09/28/impl-trait/ - https://github.com/rust-lang…

To be clear, the issue here isn't so much stack vs heap, as much as how many heap allocations are happening. In practice, you build up a really big combined future on the stack, wh…

Yes -- the blog post didn't go into details about this, but Futures in general have an error type as well, and all the combinators know how to propagate errors correctly. (There's …