spir wrote: > On Sun, 21 Nov 2010 18:21:48 +0100 > Don <[email protected]> wrote: > >> spir wrote: >>> On Sun, 21 Nov 2010 03:17:57 -0800 >>> Jonathan M Davis <[email protected]> wrote: >>> >>>> You're not losing _anything_ out of the deal except that you wouldn't do >>>> obj.toString(). Instead you'd do to!string(obj). >>> I'm usually not using toString(), it's supported by the language. What >>> about format("%s:%s", a,b)? Will it still call toString implicitely, or >>> writeTo a buffer, or what else? >>> >>> Anyway, I cannot see any advantage in deprecating toString() for every >>> programmer in every use case, just for hypothetical efficiency issues >> The efficiency issues are important, > > 1. Please bring concrete cases of apps that do not work well because of > toString and would work fine just by replacing it with writeTo.
Please bring a concrete example of code that would suffer from the
proposal.
Jerome
--
mailto:[email protected]
http://jeberger.free.fr
Jabber: [email protected]
signature.asc
Description: OpenPGP digital signature
