Keep an eye out on version updates for Tokio 1.0
dt665m opened this issue · comments
Summary of the Feature
Tokio finally hit 1.0, guaranteeing api stability for 3 years, which means all our deps should be rushing (at their own pace) to lock on.
Problem
Lots of our deps are fragmented around tokio 0.2 and tokio 0.3. This causes some confusion and requires tiptoeing when selecting dependencies. Tokio 1.0 should alleviate this pain.
Proposal
Watch our larger dependencies
v0.6.2 currently is a preliminary effort to go to tokio 1.
Technical debt:
- Using a Fork/PR for actix-extras (actix-cors and actix-httpauth)
- Using a Fork/PR for sqlx until 5.0 is ready with tokio 1
- Juniper-actix functions have been copied and moved into atb-rs until they also update to actix 0.11 stable. It is not likely that they will update unless actix goes out of beta channel
Watch:
Update
- actix/actix-web has betas that work
- sqlx current master already at tokio1
- eventstore current master already at tokio1
Not Ready
- actix-extra
- juniper-actix
1.0 is now stable in the ecosystem, closing