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

Correct Substrate Installation Link and Rust Command Terminology #1431

Closed
wants to merge 1 commit into from

Conversation

savvar9991
Copy link

@savvar9991 savvar9991 commented Feb 28, 2025

1.Updated Substrate installation link

Before:

$ curl https://getsubstrate.io/ -ssf | bash -s -- --fast
After:

$ curl https://docs.substrate.io/install/ -ssf | bash -s -- --fast**

Explanation: Replaced an outdated Substrate installation link with the correct one (docs.substrate.io/install/).

2. Fixed incorrect command (non_std → no_std)

Before:
Right now, if non_std is required, default-features = false must be set in the root Cargo.toml file (related to this issue). Otherwise, it will have no effect, causing your compilation to fail.

After:
Right now, if no_std is required, default-features = false must be set in the root Cargo.toml file (related to this issue). Otherwise, it will have no effect, causing your compilation to fail.

Explanation:
Fixed a typo in the flag name: "non_std" was incorrect and was replaced with "no_std", which is the correct Rust terminology for using a standard library-free environment.
Elimination of Potential Errors: The incorrect use of the term "non_std" could lead to misunderstandings about how to properly configure the project, which may cause compilation issues. Correcting this terminology helps prevent such errors.

@Dinonard
Copy link
Member

Dinonard commented Mar 1, 2025

Thank you but we don't accept what is essentially typo fixes.

@Dinonard Dinonard closed this Mar 1, 2025
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.

2 participants