async keyword throws IDE error
See original GitHub issueEnvironment
- IntelliJ Rust plugin version: 0.2.114.2151-193
- Rust toolchain version: 1.41.0 (5e1a79984 2020-01-27)
- IDE name and version: WebStorm 2019.3
- Operating system: Windows10
Problem description
async
keywork seems to not get recognized by the IDE/plugin. Error says: “This feature is only available in Edition 2018”, but I have a sibling file Cargo.toml with [package] edition = "2018"
Steps to reproduce
Just install plugin, and if you want to reproduce, clone deno, many files have this problem.
Is there anything I’m doing wrong or that I can do to try to fix this?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:8 (1 by maintainers)
Top Results From Across the Web
handle response type async/await - IDE error - Stack Overflow
The error message is telling you that you are assigning void to rules. This is because void is the result of the last...
Read more >How to avoid uncaught async errors in Javascript
Errors in async functions that are not handled show in the console and can cause problems. Let's see how to prevent them.
Read more >Async/Await Error Handling - Beginner JavaScript - Wes Bos
We will talk about error handling strategies for async await in this lesson. Because there is no .then() that we are chaining on...
Read more >Optional, throws, Result, async/await - NSHipster
We set up a query, pass an an empty inout reference to SecItemCopyMatching and then, depending on the status code we get back,...
Read more >How to Throw Errors From Async Functions in JavaScript?
Async functions and async methods do not throw errors in the strict sense. Async functions and async methods always return a Promise, either ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m getting this issue as well. When I change my crate’s cargo file from 2021 to 2018 it goes away, but obviously that isn’t much of a fix.
Still an issue, how do I re-open this?