rust/tests/ui/structs-enums/class-poly-methods-cross-crate.rs

// run-pass
// aux-build:cci_class_6.rs

extern crate cci_class_6;
use cci_class_6::kitties::cat;

pub fn main() {
  let mut nyan : cat<char> = cat::<char>(52_usize, 99, vec!['p']);
  let mut kitty = cat(1000_usize, 2, vec!["tabby".to_string()]);
  assert_eq!(nyan.how_hungry, 99);
  assert_eq!(kitty.how_hungry, 2);
  nyan.speak(vec![1_usize,2_usize,3_usize]);
  assert_eq!(nyan.meow_count(), 55_usize);
  kitty.speak(vec!["meow".to_string(), "mew".to_string(), "purr".to_string(), "chirp".to_string()]);
  assert_eq!(kitty.meow_count(), 1004_usize);
}
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`
Generic classes and generic class methods work cross-crate Classes can have ty params now. So can methods inside classes. That was probably true before, but now it should still work if you call methods in a class that's defined in a different crate. Yay! 2012-04-10 12:52:06 -05:00			`// aux-build:cci_class_6.rs`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 15:13:15 -05:00
extern mod => extern crate This was previously implemented, and it just needed a snapshot to go through 2014-02-14 12:10:06 -06:00			`extern crate cci_class_6;`
Add appropriate #[feature] directives to tests 2013-10-02 22:00:54 -05:00			`use cci_class_6::kitties::cat;`
Generic classes and generic class methods work cross-crate Classes can have ty params now. So can methods inside classes. That was probably true before, but now it should still work if you call methods in a class that's defined in a different crate. Yay! 2012-04-10 12:52:06 -05:00
check-fast fallout from removing export, r=burningtree 2013-02-01 21:43:17 -06:00			`pub fn main() {`
Changed most vec! invocations to use square braces Most of the Rust community agrees that the vec! macro is clearer when called using square brackets [] instead of regular brackets (). Most of these ocurrences are from before macros allowed using different types of brackets. There is one left unchanged in a pretty-print test, as the pretty printer still wants it to have regular brackets. 2016-10-29 16:54:04 -05:00			`let mut nyan : cat<char> = cat::<char>(52_usize, 99, vec!['p']);`
			`let mut kitty = cat(1000_usize, 2, vec!["tabby".to_string()]);`
Use assert_eq! rather than assert! where possible 2013-05-18 21:02:45 -05:00			`assert_eq!(nyan.how_hungry, 99);`
			`assert_eq!(kitty.how_hungry, 2);`
Changed most vec! invocations to use square braces Most of the Rust community agrees that the vec! macro is clearer when called using square brackets [] instead of regular brackets (). Most of these ocurrences are from before macros allowed using different types of brackets. There is one left unchanged in a pretty-print test, as the pretty printer still wants it to have regular brackets. 2016-10-29 16:54:04 -05:00			`nyan.speak(vec![1_usize,2_usize,3_usize]);`
Update suffixes en masse in tests using `perl -p -i -e` 2015-02-18 04:42:01 -06:00			`assert_eq!(nyan.meow_count(), 55_usize);`
Changed most vec! invocations to use square braces Most of the Rust community agrees that the vec! macro is clearer when called using square brackets [] instead of regular brackets (). Most of these ocurrences are from before macros allowed using different types of brackets. There is one left unchanged in a pretty-print test, as the pretty printer still wants it to have regular brackets. 2016-10-29 16:54:04 -05:00			`kitty.speak(vec!["meow".to_string(), "mew".to_string(), "purr".to_string(), "chirp".to_string()]);`
Update suffixes en masse in tests using `perl -p -i -e` 2015-02-18 04:42:01 -06:00			`assert_eq!(kitty.meow_count(), 1004_usize);`
Generic classes and generic class methods work cross-crate Classes can have ty params now. So can methods inside classes. That was probably true before, but now it should still work if you call methods in a class that's defined in a different crate. Yay! 2012-04-10 12:52:06 -05:00			`}`