mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix a comment.

Browse Source 
Compiling any part of the compiler will almost certainly require
Nightly.
This commit is contained in:
Nicholas Nethercote 2023-10-02 16:04:35 +11:00
parent 5f4177a786
commit 57397de2c9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
compiler/rustc_log/src/lib.rs
View File

@ -23,10 +23,10 @@
//! } //! }
//! ``` //! ```
//! //!
//! Now `LOG=debug cargo run` will run your minimal main.rs and show //! Now `LOG=debug cargo +nightly run` will run your minimal main.rs and show
//! rustc's debug logging. In a workflow like this, one might also add //! rustc's debug logging. In a workflow like this, one might also add
//! `std::env::set_var("LOG", "debug")` to the top of main so that `cargo //! `std::env::set_var("LOG", "debug")` to the top of main so that `cargo
//! run` by itself is sufficient to get logs. //! +nightly run` by itself is sufficient to get logs.
//! //!
//! The reason rustc_log is a tiny separate crate, as opposed to exposing the //! The reason rustc_log is a tiny separate crate, as opposed to exposing the
//! same things in rustc_driver only, is to enable the above workflow. If you //! same things in rustc_driver only, is to enable the above workflow. If you