Thanks for citing this
I think this is an important point. Nothing should parse, convert or manipulate the debug description. Our logging systems aren’t doing that. They aren’t even calling the debug description API directly. However, as I said above, swift-log is relying heavily on description which is often calling debugDescription. Furthermore, errors such as the decoding and encoding errors here are often logged. If this proposal is getting accepted as is, then this will most likely break a few logging backends. To make matters worse the only workaround that I see for those backends is to parse the description and sanitize it which is too costly to do in every single log.