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

docs: recommend use of nightly Rust for local development #4601

Closed
wants to merge 2 commits into from

Conversation

thomaseizinger
Copy link
Contributor

Description

Using nightly Rust for local development is regarded as useful because it helps detecting compiler bugs early and tends to provide better diagnostics.

Related: #4575.

Notes & open questions

I am not sure we want to go as far as actually recommending this. Happy to leave this PR open for a bit and experiment ourselves first, how good using nightly Rust for local dev is.

Change checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • A changelog entry has been made in the appropriate crates

@thomaseizinger thomaseizinger requested a review from mxinden October 9, 2023 00:11
@mxinden
Copy link
Member

mxinden commented Oct 11, 2023

Given that we compile with nightly on CI and given that we fail on warnings, isn't that good enough? What bug in the past would have been prevented if we were to run nightly locally?

@thomaseizinger
Copy link
Contributor Author

Given that we compile with nightly on CI and given that we fail on warnings, isn't that good enough? What bug in the past would have been prevented if we were to run nightly locally?

No particular bug. Rocket recommends the same thing for better macro diagnostics for example.

Just wanted to help users in not having a different setup than in Ci!

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