5 commits

Author	SHA1	Message	Date
Sean McArthur	44440e5c18	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]	2015-01-06 14:49:42 -08:00
Huon Wilson	4016c729f1	Remove use of associated_types feature gate from tests.	2015-01-05 20:00:10 +11:00
Jorge Aparicio	4f4ae538ae	fix rpass/cfail tests	2015-01-03 09:34:05 -05:00
Niko Matsakis	7f6177e646	Fix fallout from changes. In cases where stage0 compiler is needed, we ... cannot use an `as` expression to coerce, so I used a one-off function instead (this is a no-op in stage0, but in stage1+ it triggers coercion from the fn pointer to the fn item type).	2014-12-22 12:27:07 -05:00
Patrick Walton	d1dcd19d26	librustc: Make references to functions not have static lifetime. ... This breaks code like: struct A<'a> { func: &'a fn() -> Option<int> } fn foo() -> Option<int> { ... } fn create() -> A<'static> { A { func: &foo } } Change this code to not take functions by reference. For example: struct A { func: extern "Rust" fn() -> Option<int> } fn foo() -> Option<int> { ... } fn create() -> A { A { func: foo } } Closes #13595. [breaking-change]	2014-07-24 15:29:26 -07:00