Bug or Feature? compile error: to!string(const Object)

[Wanderer via Digitalmars-d]

On Tuesday, 1 July 2014 at 01:13:25 UTC, Jonathan M Davis via 
Digitalmars-d wrote:
> The long term plan is to remove toString, opEquals, toHash, and 
> opCmp from
> Object so that the derived classes can decide whether to make 
> them const or
> not. Unlike Java and C#, we have proper templates, so we can 
> templatize all of
> the stuff in the runtime which uses those functions so that 
> they don't have to
> be on Object.

Remove toString from the root of the object hierarchy?? How do 
you plan to implement ~ operator for constructing strings? It 
should work with any types, even unbeknown to each other.