_Comment made by: ataggart_
Despite the examples given, many real-world log entries contain not only structured data, but also human-readable explanatory text. As such, switching to always using `pr-str` will emit quotes and escaped characters when _not_ desired, and with no way to work around it (unlike how one can work around the current issue by manually wrapping values with `pr-str`). This kind of breaking change is a no-go.
That said, it may be reasonable to add _new_ macros to handle this common point of friction.
A variant of `logp` is problematic since in the common case of mixing text and data we can’t know for certain which args the user intends to be treated which way.
A variant of `logf` might work, whereby all format args are mapped over `pr-str`, with explanatory text residing in the format string.