Unable to specify `edition2021` in order to use unstable packages in Rust

Question

I want to run an example via Cargo but I am facing an error:

error: failed to parse manifest at `/Users/aviralsrivastava/dev/subxt/Cargo.toml`

The full stacktrace is:

error: failed to parse manifest at `/Users/aviralsrivastava/dev/subxt/Cargo.toml`

Caused by:
  feature `edition2021` is required

  The package requires the Cargo feature called `edition2021`, but that feature is not stabilized in this version of Cargo (1.56.0-nightly (b51439fd8 2021-08-09)).
  Consider adding `cargo-features = ["edition2021"]` to the top of Cargo.toml (above the [package] table) to tell Cargo you are opting in to use this unstable feature.
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2021 for more information about the status of this feature.

Based on the suggestion, I go ahead and modify the Cargo.toml:

  Consider adding `cargo-features = ["edition2021"]` to the top of Cargo.toml (above the [package] table) to tell Cargo you are opting in to use this unstable feature.
diff --git a/Cargo.toml b/Cargo.toml
index 26a02c7..186d09b 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,6 +1,6 @@
 [workspace]
 members = [".", "cli", "codegen", "macro"]
-
+cargo-features = ["edition2021"]
 [package]
 name = "subxt"
 version = "0.15.0"
(END)

I still face the same error as if nothing was changed in the toml file.

How do I resolve the above error in order to use unstable packages?

What does that mean? Sorry I am new here. Do you mean subxt downgrading or substrate node? — Aviral Srivastava, Nov 05 '21 at 05:38
How do I do that? `rustup default ` ? Which version should I move to? Thanks — Aviral Srivastava, Nov 05 '21 at 05:41
It did not work out. Same error.https://pastebin.com/rtxZdtLi — Aviral Srivastava, Nov 05 '21 at 05:56
Then what about `rustup default nightly && rustup update` I clone the subxt repo, which works fine for me. — AurevoirXavier, Nov 05 '21 at 05:58
@AviralSrivastava Can you please support the Substrate StackExchange proposal: https://area51.stackexchange.com/proposals/126136 — Shawn Tabrizi, Dec 16 '21 at 13:03
Haha @ShawnTabrizi sir, I already did. Couple of days ago when I saw the word in Discord. Gonna circulate it among my circle too. — Aviral Srivastava, Dec 17 '21 at 04:15

AurevoirXavier · Accepted Answer · 2021-12-14T14:09:33.047

58

Update the Rust to satisfy the new edition 2021.

rustup default nightly && rustup update

Thanks to @ken. Yes, you can use the stable channel too!

But I love nightly personally.

edited Dec 14 '21 at 14:09

answered Nov 06 '21 at 13:24

AurevoirXavier

2,543
2
17
25

2

I ran into this issue this morning using my Intel Mac and just ran `rustup update` on the stable branch and that was enough ... had been using 2021 edition without issue on my M1 Mac all weekend without issue but maybe it was running the updated version. Anyway, 2021 is a stable release now. – ken Dec 13 '21 at 13:27

score 16 · Answer 2 · answered Feb 02 '22 at 07:05

16

Edition 2021 is now part of the stable channel.

As what happened to me, you probably just need to update your stable version by running rustup update stable.

That should fix the issue, and not require you to switch over to the nightly channel.

answered Feb 02 '22 at 07:05

chai_and_kaapi

181
1
5

2

this should be the top answer now! – Ben Usman Jul 04 '22 at 20:16

score 5 · Answer 3 · answered Dec 12 '21 at 09:56

5

Try:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
source $HOME/.cargo/env && rustup default nightly && rustup update

answered Dec 12 '21 at 09:56

Aviel Yosef

533
5
10

This worked for me – KhoPhi Feb 07 '22 at 16:57

score 0 · Answer 4 · answered Jun 19 '22 at 17:58

Seen this error twice when working with Solana. You can get this error if Solana is not up to date. Update it with sh -c "$(curl -sSfL https://release.solana.com/v1.10.26/install)"

Or preferably find the latest version and instructions here https://docs.solana.com/cli/install-solana-cli-tools

score 0 · Answer 5 · answered Jun 28 '22 at 10:22

0

Some machines (including those with M1 chips) may be unable to build

answered Jun 28 '22 at 10:22

zinderud

27
2

Unable to specify `edition2021` in order to use unstable packages in Rust

5 Answers5

Linked