Skip to content
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

Update async unsafe fn ordering in parser #3047

Merged
merged 1 commit into from
Feb 7, 2020
Merged

Update async unsafe fn ordering in parser #3047

merged 1 commit into from
Feb 7, 2020

Conversation

kiljacken
Copy link
Contributor

As of rust-lang/rust#61319 the correct order for functions that are both unsafe and async is: async unsafe fn and not unsafe async fn.

This commit updates the parser tests to reflect this, and corrects parsing behavior to accept the correct ordering.

Fixes #3025

As of rust-lang/rust#61319 the correct order for functions that are both
unsafe and async is: `async unsafe fn` and not `unsafe async fn`.

This commit updates the parser tests to reflect this, and corrects
parsing behavior to accept the correct ordering.

Fixes #3025
@matklad
Copy link
Member

matklad commented Feb 7, 2020

bors r+

bors bot added a commit that referenced this pull request Feb 7, 2020
3047: Update async unsafe fn ordering in parser r=matklad a=kiljacken

As of rust-lang/rust#61319 the correct order for functions that are both unsafe and async is: `async unsafe fn` and not `unsafe async fn`.

This commit updates the parser tests to reflect this, and corrects parsing behavior to accept the correct ordering.

Fixes #3025

Co-authored-by: Emil Lauridsen <mine809@gmail.com>
@bors
Copy link
Contributor

bors bot commented Feb 7, 2020

Build succeeded

  • Rust (macos-latest)
  • Rust (ubuntu-latest)
  • Rust (windows-latest)
  • TypeScript

@bors bors bot merged commit 73ec2ab into rust-lang:master Feb 7, 2020
@kiljacken kiljacken deleted the parse-async-unsafe-fn branch February 17, 2020 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to parse unsafe async fn
2 participants