Book: Standard Input is out-of-date

[KingOfThePirates]

http://doc.rust-lang.org/book/standard-input.html

When running the old I/O Standard library, I get an error that the compiler won't admit.

Example:

use std::old_io; // error: use of unstable library feature 'old_io'
                 // warning: use of deprecated item, #[warn(deprecated)] on by default
fn main() {
    println!("Type something!");

    let input = old_io::stdin().read_line().ok().expect("Failed to read line"); // error: use of unstable library feature 'old_io'
                                                                                // error: use of unstable library feature 'old_io'
                                                                                // warning: use of deprecated item, #[warn(deprecated)] on by default
                                                                                // warning: use of deprecated item, #[warn(deprecated)] on by default
    println!("{}", input);

}

[steveklabnik]

Thanks! These are the ones we can't run automated tests for :(

[makramkd]

Also, not sure if this is a typo or not since I am new to Rust (started learning yesterday!) but the nightly version of the docs has this instead:

corefn main() {
    println!("Type something!");

    let input = std::old_io::stdin().read_line().ok().expect("Failed to read line");

    println!("{}", input);
}

I'm not sure what corefn is: I'm assuming it should just be fn? See : http://doc.rust-lang.org/book/standard-input.html

[makramkd]

After posting this inquiry on StackOverflow Shepmaster gave the following workaround that will hopefully help whoever has this problem:

fn main() {
    println!("Type something: ");

    let mut s = String::new();
    let input = std::io::stdin().read_line(&mut s).ok().expect("Failed to read line!");

    println!("Here's what you said: {}", s);
}

[kaungst]

This is also an issue here
http://doc.rust-lang.org/1.0.0-alpha.2/book/guessing-game.html

[steveklabnik]

That's for alpha 2. For that release, it should be fine, but regardless, that release is out.