Jim Blandy

Nothing has changed on this question. That reference to "gfx-rs#797" seems to be a broken link of some sort; I can't find what it's referring to. Maybe fallout from repo...

(The `hello-triangle` example doesn't respect `WGPU_BACKEND`. Edited issue description to use `cube` instead, which does.)

Perhaps try updating your clippy?

Note that the `warp::path("static")` is essential to the problem, since browsers automatically request `/` when the URL's path is empty (that is, requesting `localhost:3030` always sends `GET / HTTP/1.1`), so...

> If you look at the way other servers handle requests for URLs whose paths lack a trailing slash, you'll see that they first send a `302 FOUND` response with...

This proposal is meant to address an important problem: crate authors need a way to spawn without having to take on Tokio and async-std as a dependency that may clash...

Having the `Executor` trait methods take already-boxed futures allows the trait to be object safe. But executors go to great lengths to minimize the number of dynamic allocations per spawn...

> So what would the api for that look like? I'm not very familiar with the internals of executors. I am not sure, honestly. It just seemed to me that...

Yeah, bump allocators are only simple because they impose restrictions on the order in which things can be freed. I don't think we know anything about the order in which...

I'd like to put in a vote for this. As I said on Discord: > Aside from being handy for non-Send futures, I found it helpful in writing an explanation...