-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Listing 12-14: use minigrep;
instead of extern crate minigrep;
results in error
#1676
Comments
I'm running into the same issue as well, and the fix above worked for me. |
Hi @carols10cents, Thank you for the reply — I see now that the book is in lockstep with the latest release of Rust and the version I installed last week (1.30.1) doesn't include the |
Yep, the edition switchover is a bit confusing right now. Glad this solved
your problem!
…On Mon, Dec 10, 2018, 12:54 PM John Vivian ***@***.*** wrote:
Hi @carols10cents <https://github.com/carols10cents>,
Thank you for the reply — I see now that the book is in lockstep with the
latest release of Rust and the version I installed last week (1.30.1)
doesn't include the edition="2018" in Cargo.toml. I updated via rustup
update and added edition = "2018" which resolved my issue. Thank you very
much! I'll go ahead and close this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1676 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAL1Ul1JiRUSzMA2ZSdy8SBw_AVaqhVKks5u3p_JgaJpZM4ZKYV4>
.
|
I try to re-create project with --lib ( |
In case anyone else stumbles upon this in the future the correct answer is actually to run |
in my case version is |
I'm following the current live version of the Rust book (master on Github) and encountered the following issue:
Listing 12-14 states to use
use minigrep;
"... to bring the library crate into the binary crate". Yet when I do that I get the following compile errors when callingcargo run
:If I change
use minigrep;
toextern crate minigrep;
the problem goes away.I'd be happy to open a pull request if this is a legitimate bug.
The text was updated successfully, but these errors were encountered: