rust/tests/ui/issues/issue-1696.rs

// run-pass
use std::collections::HashMap;

pub fn main() {
    let mut m = HashMap::new();
    m.insert(b"foo".to_vec(), b"bar".to_vec());
    println!("{:?}", m);
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 07:18:55 -05:00			`// run-pass`
Fallout from the libcollections movement 2014-05-29 21:03:06 -05:00			`use std::collections::HashMap;`
test: Add a test for #1696 2012-02-22 23:17:09 -06:00
check-fast fallout from removing export, r=burningtree 2013-02-01 21:43:17 -06:00			`pub fn main() {`
rename Linear{Map,Set} => Hash{Map,Set} 2013-04-03 08:28:36 -05:00			`let mut m = HashMap::new();`
Rename functions in the CloneableVector trait * Deprecated `to_owned` in favor of `to_vec` * Deprecated `into_owned` in favor of `into_vec` [breaking-change] 2014-07-16 15:37:28 -05:00			`m.insert(b"foo".to_vec(), b"bar".to_vec());`
core: split into fmt::Show and fmt::String fmt::Show is for debugging, and can and should be implemented for all public types. This trait is used with `{:?}` syntax. There still exists #[derive(Show)]. fmt::String is for types that faithfully be represented as a String. Because of this, there is no way to derive fmt::String, all implementations must be purposeful. It is used by the default format syntax, `{}`. This will break most instances of `{}`, since that now requires the type to impl fmt::String. In most cases, replacing `{}` with `{:?}` is the correct fix. Types that were being printed specifically for users should receive a fmt::String implementation to fix this. Part of #20013 [breaking-change] 2014-12-20 02:09:35 -06:00			`println!("{:?}", m);`
test: Add a test for #1696 2012-02-22 23:17:09 -06:00			`}`