On Monday, 8 September 2014 at 22:54:36 UTC, Dicebot wrote:
nogc is not possible because of custom toString
that won't fix, but for default types it is nogc.
It should be possible to provide custom implementation that
throws ad Error for those cases (and thus fits the
requirements) and `toString` has sink-based overload. Are there
any reason why it doesn't help?
catching an Exception from formattedWrite just to throw an Error
and thus allowing nothrow is just silly IMO.
sink-based overloads are nice but we don't write the toString
methods of the user and so can not be sure that they are nogc.
