Actix-web: Update to std::future::Future futures/0.3

[pythoneer]

std::future::Future is now in stable with Rust 1.36.0. What are the plans for migration? I think one mayor obstacle is at which point tokio is using them right? Do they already have? i am a little bit out of the loop https://github.com/tokio-rs/tokio/pull/1218

[fafhrd91]

actix-service must be ported first. It does not depend on tokio

[leaxoy]

How about use tower::Service instead

[fafhrd91]

I tried, it does not work well. Also I don’t want to depend on external dependency. So no tower

[leaxoy]

Okey, but can we provide a bridge between actix-service and tower as an optional feature?

[fafhrd91]

There is project in actix-net repo. But I am not interested in that project. I can move it outside so other people can work on it

[naturallymitchell]

Seems like a lot's going on now, eg tokio 0.2.0-alpha-1.

[leaxoy]

Async/Await stable pr is merged in today nightly version, should we start the process to update to std::future::Future

[semtexzv]

I started the work on migrating the actix-net ecosystem, which is needed in order to convert the
actix-web libraries. Work can be seen here: https://github.com/actix/actix-net/issues/45.

[kanekv]

Are there any plans to migrate to tokio 0.2?

[Jonathas-Conceicao]

The migration has started on actix-net, there's a migration tracking issue there.

[wigy-opensource-developer]

I see this issue assigned to the 1.1 milestone. I doubt you can migrate to tokio 0.2 and async-await without breaking changes in the API. Based on that and semantic versioning the next actix-web version should be 2.0, right?

[cdbattags]

The migration has started on actix-net, there's a migration tracking issue there.

We're going to need some help starting with the actix-service folder in actix-net.

See https://github.com/actix/actix-net/pull/57.

If you'd like to help, please converse in that PR and and/or if you have work open a PR into actix-net/std-future branch.

We should be able to get this done pretty quickly just need some minds to start talking it through.

[cdbattags]

Just landed in actix-net https://github.com/actix/actix-net/pull/64

Fantastic work, @fafhrd91!

[0xpr03]

the next actix-web version should be 2.0, right?

I'm all for that, people that need futures 0.1 and fixes can then still stay on 1.X
I think a 2.0 release would also reflect the amount of work that went into the async/await port and the changes when writing async stuff for actix-web.
(In other words: please don't repeat the 1.0.2 breaking changes.)

[fafhrd91]

tracking issue #1166