toString vs. toUtf8

[Steven Schveighoffer]

"Sean Kelly" wrote
> What I discovered during a test conversion of Tango was that converting 
> all uses of toUtf8 to toString /except/ those intended to perfom UTF 
> conversions reduced code clarity, and left me unsure as to which name I 
> would actually use in a given situation.  For example, there is quite a 
> bit of code in the text and io packages which convert an arbitrary type to 
> a char[] for output, etc.  So by making this change I was left with some 
> conversions using toString and others using toUtf8, toUtf16, and toUtf32, 
> not to mention the fromXxx versions of these same functions. As this is 
> template code, the choice between toString and toUtf8 in a given situation 
> was unclear.

Can you give an example file for this problem?  It would be easier to 
understand your problem if I knew exactly what you were talking about.  An 
actual example is fine, it doesn't need to be minimized (i.e. "take a look 
at tango/io/X.d")

-Steve