> How do people feel about deprecating Serializable in 7.4 and > removing in 8.0 (not as part of this RFC but a separate one)? The > deprecation warning would only be thrown if Serializable is implemented but > the class has no __serialize/__unserialize. The timeline would be a bit > aggressive in that we'd be introducing the replacement in the same release > as the deprecation, something I'd usually try to avoid. >
I'd feel fine. The plan is aggressive, but Serializable easily produces broken payloads right now, so we need to move away from it as quickly as possible. You didn't mention it, but keeping __sleep/__wakeup as is in 7.4 is fine to me: they do no harm. Deprecating them might be considered in 8.1, but they don't need the same aggressive plan to me. Nicolas
