-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
async fn
inside inherent impl produces generic parse error on 2015 edition
#53714
Labels
Comments
Since async blocks and some versions of the final |
withoutboats
added
the
A-diagnostics
Area: Messages for errors, warnings, and lints
label
Feb 22, 2019
Centril
added a commit
to Centril/rust
that referenced
this issue
Feb 27, 2019
…n, r=varkor Deny `async fn` in 2015 edition This commit prevents code using `async fn` from being compiled in Rust 2015 edition. Compiling code of the form: ```rust async fn foo() {} ``` Will now result in the error: ``` error[E0670]: `async fn` is not permitted in the 2015 edition --> async.rs:1:1 | 1 | async fn foo() {} | ^^^^^ error: aborting due to error For more information about an error, try `rustc --explain E0670`. ``` This resolves rust-lang#58652 and also resolves rust-lang#53714. r? @varkor
Centril
added a commit
to Centril/rust
that referenced
this issue
Feb 27, 2019
…n, r=varkor Deny `async fn` in 2015 edition This commit prevents code using `async fn` from being compiled in Rust 2015 edition. Compiling code of the form: ```rust async fn foo() {} ``` Will now result in the error: ``` error[E0670]: `async fn` is not permitted in the 2015 edition --> async.rs:1:1 | 1 | async fn foo() {} | ^^^^^ error: aborting due to error For more information about an error, try `rustc --explain E0670`. ``` This resolves rust-lang#58652 and also resolves rust-lang#53714. r? @varkor
Centril
added a commit
to Centril/rust
that referenced
this issue
Feb 27, 2019
…n, r=varkor Deny `async fn` in 2015 edition This commit prevents code using `async fn` from being compiled in Rust 2015 edition. Compiling code of the form: ```rust async fn foo() {} ``` Will now result in the error: ``` error[E0670]: `async fn` is not permitted in the 2015 edition --> async.rs:1:1 | 1 | async fn foo() {} | ^^^^^ error: aborting due to error For more information about an error, try `rustc --explain E0670`. ``` This resolves rust-lang#58652 and also resolves rust-lang#53714. r? @varkor
Centril
added a commit
to Centril/rust
that referenced
this issue
Feb 27, 2019
…n, r=varkor Deny `async fn` in 2015 edition This commit prevents code using `async fn` from being compiled in Rust 2015 edition. Compiling code of the form: ```rust async fn foo() {} ``` Will now result in the error: ``` error[E0670]: `async fn` is not permitted in the 2015 edition --> async.rs:1:1 | 1 | async fn foo() {} | ^^^^^ error: aborting due to error For more information about an error, try `rustc --explain E0670`. ``` This resolves rust-lang#58652 and also resolves rust-lang#53714. r? @varkor
Centril
added a commit
to Centril/rust
that referenced
this issue
Feb 27, 2019
…n, r=varkor Deny `async fn` in 2015 edition This commit prevents code using `async fn` from being compiled in Rust 2015 edition. Compiling code of the form: ```rust async fn foo() {} ``` Will now result in the error: ``` error[E0670]: `async fn` is not permitted in the 2015 edition --> async.rs:1:1 | 1 | async fn foo() {} | ^^^^^ error: aborting due to error For more information about an error, try `rustc --explain E0670`. ``` This resolves rust-lang#58652 and also resolves rust-lang#53714. r? @varkor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
When compiling for the 2018 edition, rustc allows
async fn
both outside of an impl and within an inherent impl.When compiling for the 2015 edition,
async fn
works outside of an impl, but putting one inside an inherent impl produces this error:Either this should be allowed, or it should result in a better error message that recommends switching to the 2018 edition.
The text was updated successfully, but these errors were encountered: