-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tokio 0.2 #[tokio::main] regression #1833
Comments
I was too. quick to open the issue :( It seems that everything in the new version is behind feature flags. In order fo rthe #[tokio::main] macro to work, one needs:
it would be nice if this is mentioned in the readme |
Can you point where in the readme? I believe it mentions the “full” feature flag, which includes macros but it is likely we missed somewhere. |
The feature flags are not mentioned at all: https://github.com/tokio-rs/tokio/blob/master/README.md I've just seen them mentioned in your blogpost in reddit :) What about appending part of the tour of tokio section content to the existing content in the "overview" section ?
|
As of tokio 0.2, features are hidden behind flags. For example, macros require the `macro` feature. See tokio-rs/tokio#1833 for a more detailed description. The easiest way to stay up-to-date is by enabling the `full` feature flag, which is analog to the previous behavior. This fixes `cargo install`. Also, the `async_await` feature can be removed as it is stable since rustc 1.39.
As of tokio 0.2, features are hidden behind flags. For example, macros require the `macro` feature. See tokio-rs/tokio#1833 for a more detailed description. The easiest way to stay up-to-date is by enabling the `full` feature flag, which is analog to the previous behavior. This fixes `cargo install`. Also, the `async_await` feature can be removed as it is stable since rustc 1.39.
As of tokio 0.2, features are hidden behind flags. For example, macros require the `macro` feature. See tokio-rs/tokio#1833 for a more detailed description. The easiest way to stay up-to-date is by enabling the `full` feature flag, which is analog to the previous behavior. This fixes `cargo install`.
Hi, |
Closing in favor of #2626. |
Version
Both tokio 0.2.0 and 0.2.1
`--> cargo tree | grep tokio
└── tokio v0.2.1
Platform
Darwin C02XC3DFJGH6 18.7.0 Darwin Kernel Version 18.7.0: Tue Aug 20 16:57:14 PDT 2019; root:xnu-4903.271.2~2/RELEASE_X86_64 x86_64
Description
When I try to compile the most basic example:
cargo toml:
I get the following error:
If I revert to 0.2.0-alpha.6 it builds successfully. This is slimmed-down version of the example in the README: https://github.com/tokio-rs/tokio
The text was updated successfully, but these errors were encountered: